Partial control resource set handling

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive an indication of an initial downlink bandwidth for the UE. The UE may receive, via a master information block (MIB), configuration information for a control resource set (CORESET) associated with physical downlink control channel (PDCCH) monitoring for initial access, where the configuration information indicates a frequency domain resource allocation for the CORESET, and where the frequency domain resource allocation for the CORESET is at least partially outside of the initial downlink bandwidth. The UE may receive one or more PDCCH messages associated with the CORESET based at least in part on at least one of modifying a resource mapping of the CORESET or modifying the initial downlink bandwidth. Numerous other aspects are provided.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and specifically, to techniques and apparatuses forpartial control resource set (CORESET) handling.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (for example,bandwidth or transmit power). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, orglobal level. New Radio (NR), which may be referred to as 5G, is a setof enhancements to the LTE mobile standard promulgated by the 3GPP. NRis designed to better support mobile broadband internet access byimproving spectral efficiency, lowering costs, improving services,making use of new spectrum, and better integrating with other openstandards using orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM orsingle-carrier frequency division multiplexing (SC-FDM) (also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, aswell as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR,and other radio access technologies remain useful.

A potential control region of a slot may be referred to as a controlresource set (CORESET) and may be structured to support an efficient useof resources, such as by flexible configuration or reconfiguration ofresources of the CORESET for one or more physical downlink controlchannels (PDCCHs). In some cases, a CORESET may be associated withinitial access for a wireless communication system, such as a CORESET 0.A configuration of the CORESET associated with initial access may beconfigured by broadcasted system information, such as via a masterinformation block (MIB). In some cases, a user equipment (UE) may beassociated with a downlink bandwidth for initial access with thewireless communication system (for example, an initial downlinkbandwidth or an initial downlink bandwidth part (BWP)). The downlinkbandwidth for initial access with the wireless communication system maybe associated with a limited size for some UEs. For example, some UEs ina wireless network may be associated with a less advanced capability(such as a lower capability or a reduced capability) as compared toother UEs in the wireless network. The downlink bandwidth for initialaccess for the UEs with the less advanced capability may be smaller (inthe frequency domain) than the downlink bandwidth for initial access forthe UEs with a more advanced capability. However, as the configurationof the CORESET associated with initial access may be configured bybroadcasted system information, the same CORESET may be configured forall UEs in the wireless network.

As a result, a portion of a frequency domain resource allocation (forexample, one or more control channel elements (CCEs) or resource blocks(RBs)) of the CORESET may be configured outside of the downlinkbandwidth for initial access for a UE. Because a portion of thefrequency domain resource allocation (for example, one or more CCEs) ofthe CORESET may be outside of the downlink bandwidth for initial access,the UE may be unable to receive or decode some of the CCEs or RBs of theCORESET. Because the UE may be unable to receive a portion of theCORESET, a communication performance of the UE may be degraded. Forexample, an aggregation level of PDCCH candidates associated with theCORESET may be reduced. The reduced aggregation level may cause adegradation in the communication performance of the UE.

SUMMARY

Some aspects described herein relate to a user equipment (UE) forwireless communication. The UE may include at least one processor and atleast one memory, communicatively coupled with the at least oneprocessor, that stores processor-readable code. The processor-readablecode, when executed by the at least one processor, may be configured tocause the UE to receive an indication of an initial downlink bandwidthfor the UE. The processor-readable code, when executed by the at leastone processor, may be configured to cause the UE to receive, via amaster information block (MIB), configuration information for a controlresource set (CORESET) associated with physical downlink control channel(PDCCH) monitoring for initial access, wherein the configurationinformation indicates a frequency domain resource allocation for theCORESET, and wherein the frequency domain resource allocation for theCORESET is at least partially outside of the initial downlink bandwidth.The processor-readable code, when executed by the at least oneprocessor, may be configured to cause the UE to receive one or morePDCCH messages associated with the CORESET based at least in part on atleast one of modifying a resource mapping of the CORESET or modifyingthe initial downlink bandwidth.

Some aspects described herein relate to a base station for wirelesscommunication. The base station may include at least one processor andat least one memory, communicatively coupled with the at least oneprocessor, that stores processor-readable code. The processor-readablecode, when executed by the at least one processor, may be configured tocause the base station to transmit, to a UE, an indication of an initialdownlink bandwidth for the UE. The processor-readable code, whenexecuted by the at least one processor, may be configured to cause thebase station to transmit, to the UE via an MIB, configurationinformation for a CORESET associated with PDCCH monitoring for initialaccess, wherein the configuration information indicates a frequencydomain resource allocation for the CORESET, and wherein the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth. The processor-readable code, whenexecuted by the at least one processor, may be configured to cause thebase station to transmit, to the UE, one or more PDCCH messagesassociated with the CORESET based at least in part on indicating anaction to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include receiving anindication of an initial downlink bandwidth for the UE. The method mayinclude receiving, via an MIB, configuration information for a CORESETassociated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth. The method may include receiving one or more PDCCHmessages associated with the CORESET based at least in part on at leastone of modifying a resource mapping of the CORESET or modifying theinitial downlink bandwidth.

Some aspects described herein relate to a method of wirelesscommunication performed by a base station. The method may includetransmitting, to a UE, an indication of an initial downlink bandwidthfor the UE. The method may include transmitting, to the UE via an MIB,configuration information for a CORESET associated with PDCCH monitoringfor initial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth. The method mayinclude transmitting, to the UE, one or more PDCCH messages associatedwith the CORESET based at least in part on indicating an action to beperformed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to receive an indication ofan initial downlink bandwidth for the UE. The set of instructions, whenexecuted by one or more processors of the UE, may cause the UE toreceive, via an MIB, configuration information for a CORESET associatedwith PDCCH monitoring for initial access, wherein the configurationinformation indicates a frequency domain resource allocation for theCORESET, and wherein the frequency domain resource allocation for theCORESET is at least partially outside of the initial downlink bandwidth.The set of instructions, when executed by one or more processors of theUE, may cause the UE to receive one or more PDCCH messages associatedwith the CORESET based at least in part on at least one of modifying aresource mapping of the CORESET or modifying the initial downlinkbandwidth.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a base station. The set of instructions, when executedby one or more processors of the base station, may cause the basestation to transmit, to a UE, an indication of an initial downlinkbandwidth for the UE. The set of instructions, when executed by one ormore processors of the base station, may cause the base station totransmit, to the UE via an MIB, configuration information for a CORESETassociated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth. The set of instructions, when executed by one ormore processors of the base station, may cause the base station totransmit, to the UE, one or more PDCCH messages associated with theCORESET based at least in part on indicating an action to be performedby the UE when the frequency domain resource allocation for the CORESETis at least partially outside of the initial downlink bandwidth.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for receiving anindication of an initial downlink bandwidth for the apparatus. Theapparatus may include means for receiving, via an MIB, configurationinformation for a CORESET associated with PDCCH monitoring for initialaccess, wherein the configuration information indicates a frequencydomain resource allocation for the CORESET, and wherein the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth. The apparatus may include means forreceiving one or more PDCCH messages associated with the CORESET basedat least in part on at least one of modifying a resource mapping of theCORESET or modifying the initial downlink bandwidth.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for transmitting, to aUE, an indication of an initial downlink bandwidth for the UE. Theapparatus may include means for transmitting, to the UE via an MIB,configuration information for a CORESET associated with PDCCH monitoringfor initial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth. The apparatus mayinclude means for transmitting, to the UE, one or more PDCCH messagesassociated with the CORESET based at least in part on indicating anaction to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, or processing system assubstantially described with reference to and as illustrated by thedrawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples in accordance with the disclosure in order thatthe detailed description that follows may be better understood.Additional features and advantages will be described hereinafter. Theconception and specific examples disclosed may be readily utilized as abasis for modifying or designing other structures for carrying out thesame purposes of the present disclosure. Such equivalent constructionsdo not depart from the scope of the appended claims. Characteristics ofthe concepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only some typical aspects of this disclosure and aretherefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example base station incommunication with a user equipment (UE) in a wireless network inaccordance with the present disclosure.

FIG. 3 is a diagram illustrating an example resource structure forwireless communication, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of a synchronization signal(SS) hierarchy, in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example of multiplexing patterns forSS blocks (SSBs) and control resource sets (CORESETs), in accordancewith the present disclosure.

FIG. 6 is a diagram illustrating an example of a partial CORESET, inaccordance with the present disclosure.

FIGS. 7A and 7B are diagrams illustrating an example associated withpartial CORESET handling, in accordance with the present disclosure.

FIG. 8 is a flowchart illustrating an example process performed, forexample, by a UE associated with partial CORESET handling, in accordancewith the present disclosure.

FIG. 9 is a flowchart illustrating an example process performed, forexample, by a base station associated with partial CORESET handling inaccordance with the present disclosure.

FIGS. 10 and 11 are diagrams of example apparatuses for wirelesscommunication in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and are not to be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart may appreciate that the scope of the disclosure is intended to coverany aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any quantity of the aspects set forth herein. Inaddition, the scope of the disclosure is intended to cover such anapparatus or method which is practiced using other structure,functionality, or structure and functionality in addition to or otherthan the various aspects of the disclosure set forth herein. Any aspectof the disclosure disclosed herein may be embodied by one or moreelements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, or algorithms (collectivelyreferred to as “elements”). These elements may be implemented usinghardware, software, or a combination of hardware and software. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

Various aspects relate generally to partial control resource set(CORESET) handling. “Partial CORESET” may refer to a CORESET, configuredat a UE, that is associated with a frequency domain resource allocationthat is at least partially outside of an initial downlink bandwidth (forexample, an initial downlink bandwidth part (BWP) or a maximum downlinkbandwidth for initial access purposes) of the UE. Some aspects morespecifically relate to receiving, by a user equipment (UE), physicaldownlink control channel (PDCCH) messages associated with a partialCORESET based at least in part on modifying a resource mapping of thepartial CORESET or modifying the initial downlink bandwidth of the UE.For example, in some aspects, the UE may modify a control channelelement (CCE)-to-resource element group (REG) mapping using a quantityof available resource blocks (RBs) associated with the initial downlinkbandwidth. In some aspects, the UE may modify a CCE-to-REG mapping typeof the partial CORESET to a non-interleaving mapping type. In some otheraspects, the UE may modify a frequency range associated with the initialdownlink bandwidth to include the frequency domain resource allocationfor the partial CORESET based at least in part on receiving asynchronization signal block (SSB) (for example, after receiving theSSB) associated with the partial CORESET.

In some aspects, the UE may receive the PDCCH messages associated with apartial CORESET based at least in part on identifying a starting RB ofthe partial CORESET (for example, when the starting RB is outside of theinitial downlink bandwidth of the UE). The UE may identify the startingRB based at least in part on reducing a quantity of resource blocksassociated with the frequency domain resource allocation for the CORESETbased at least in part on a quantity of available resource blocks in theinitial downlink bandwidth. In some aspects, the UE may identify thestarting RB based at least in part on using common resource block indexvalues associated with a carrier bandwidth (rather than RB index valuesassociated with the initial downlink bandwidth) and an RB offsetindicated by configuration information for the partial CORESET. In someother aspects, the UE may identify the starting RB based at least inpart on virtually extending resource block indices associated with theinitial downlink bandwidth (for example, by extending index valueassociated with the initial downlink bandwidth to negative values orvalues that exceed the configured index values for the initial downlinkbandwidth).

In some aspects, the UE may receive an indication of an action to beperformed by the UE when the frequency domain resource allocation for aCORESET is at least partially outside of the initial downlink bandwidth(for example, when the CORESET is a partial CORESET). The UE may receivethe indication of the action to be performed via a CORESET zeroconfiguration (for example, a controlResourceSetZero informationelement) included in a PDCCH configuration (for example, inapdcch-ConfigSIB1 information element) indicated by a master informationblock (MIB) that configures the CORESET, via the MIB that configures theCORESET, via a system information block (SIB), or via dedicatedsignaling, among other examples.

Particular aspects of the subject matter described in this disclosurecan be implemented to realize one or more of the following potentialadvantages. In some examples, the described techniques can be used tomaintain an aggregation level of PDCCH candidates of a CORESET when afrequency domain resource allocation for the CORESET is at leastpartially outside of an initial downlink bandwidth of a UE (for example,when the CORESET is a partial CORESET). Maintaining the aggregationlevel of the PDCCH candidate(s) may improve communication performanceassociated with receiving PDCCH messages associated with the CORESET. Insome aspects, the described techniques can be used to maintain aquantity of PDCCH candidates associated with the CORESET. Maintainingthe quantity of PDCCH candidates may improve a PDCCH capacity associatedwith receiving PDCCH messages associated with the CORESET. In someaspects, the described techniques can be used to remove ambiguityassociated with a starting frequency domain resource (for example, astarting RB) of a CORESET when the starting RB is outside of the initialdownlink bandwidth of the UE. This may enable the UE to map resources(for example, RBs or CCEs) to the CORESET, monitor the CORESET (andassociated search space(s)), and receive one or more PDCCH messagesassociated with the CORESET.

FIG. 1 is a diagram illustrating an example of a wireless network inaccordance with the present disclosure. The wireless network 100 may beor may include elements of a 5G (for example, New Radio (NR)) network ora 4G (for example, Long Term Evolution (LTE)) network, among otherexamples. The wireless network 100 may include one or more base stations110 (shown as a BS 110 a, a BS 110 b, a BS 110 c, and a BS 110 d), auser equipment (UE) 120 or multiple UEs 120 (shown as a UE 120 a, a UE120 b, a UE 120 c, a UE 120 d, and a UE 120 e), or other networkentities. A base station 110 is an entity that communicates with UEs120. A base station 110 (sometimes referred to as a BS) may include, forexample, an NR base station, an LTE base station, a Node B, an eNB (forexample, in 4G), a gNB (for example, in 5G), an access point, or atransmission reception point (TRP). Each base station 110 may providecommunication coverage for a particular geographic area. In the ThirdGeneration Partnership Project (3GPP), the term “cell” can refer to acoverage area of a base station 110 or a base station subsystem servingthis coverage area, depending on the context in which the term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, or another type of cell. A macro cell maycover a relatively large geographic area (for example, severalkilometers in radius) and may allow unrestricted access by UEs 120 withservice subscriptions. A pico cell may cover a relatively smallgeographic area and may allow unrestricted access by UEs 120 withservice subscription. A femto cell may cover a relatively smallgeographic area (for example, a home) and may allow restricted access byUEs 120 having association with the femto cell (for example, UEs 120 ina closed subscriber group (CSG)). A base station 110 for a macro cellmay be referred to as a macro base station. A base station 110 for apico cell may be referred to as a pico base station. A base station 110for a femto cell may be referred to as a femto base station or anin-home base station.

The wireless network 100 may be a heterogeneous network that includesbase stations 110 of different types, such as macro base stations, picobase stations, femto base stations, or relay base stations. Thesedifferent types of base stations 110 may have different transmit powerlevels, different coverage areas, or different impacts on interferencein the wireless network 100. For example, macro base stations may have ahigh transmit power level (for example, 5 to 40 watts) whereas pico basestations, femto base stations, and relay base stations may have lowertransmit power levels (for example, 0.1 to 2 watts). In the exampleshown in FIG. 1 , the BS 110 a may be a macro base station for a macrocell 102 a, the BS 110 b may be a pico base station for a pico cell 102b, and the BS 110 c may be a femto base station for a femto cell 102 c.A base station may support one or multiple (for example, three) cells. Anetwork controller 130 may couple to or communicate with a set of basestations 110 and may provide coordination and control for these basestations 110. The network controller 130 may communicate with the basestations 110 via a backhaul communication link. The base stations 110may communicate with one another directly or indirectly via a wirelessor wireline backhaul communication link.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move in accordance with the location ofa base station 110 that is mobile (for example, a mobile base station).In some examples, the base stations 110 may be interconnected to oneanother or to one or more other base stations 110 or network nodes (notshown) in the wireless network 100 through various types of backhaulinterfaces, such as a direct physical connection or a virtual network,using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relaystation is an entity that can receive a transmission of data from anupstream station (for example, a base station 110 or a UE 120) and senda transmission of the data to a downstream station (for example, a UE120 or a base station 110). A relay station may be a UE 120 that canrelay transmissions for other UEs 120. In the example shown in FIG. 1 ,the BS 110 d (for example, a relay base station) may communicate withthe BS 110 a (for example, a macro base station) and the UE 120 d inorder to facilitate communication between the BS 110 a and the UE 120 d.A base station 110 that relays communications may be referred to as arelay station, a relay base station, or a relay.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, or asubscriber unit. A UE 120 may be a cellular phone (for example, a smartphone), a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (for example, a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (for example,a smart ring or a smart bracelet)), an entertainment device (forexample, a music device, a video device, or a satellite radio), avehicular component or sensor, a smart meter/sensor, industrialmanufacturing equipment, a global positioning system device, or anyother suitable device that is configured to communicate via a wirelessmedium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UE oran eMTC UE may include, for example, a robot, a drone, a remote device,a sensor, a meter, a monitor, or a location tag, that may communicatewith a base station, another device (for example, a remote device), orsome other entity. Some UEs 120 may be considered Internet-of-Things(IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices.Some UEs 120 may be considered a Customer Premises Equipment. A UE 120may be included inside a housing that houses components of the UE 120,such as processor components or memory components. In some examples, theprocessor components and the memory components may be coupled together.For example, the processor components (for example, one or moreprocessors) and the memory components (for example, a memory) may beoperatively coupled, communicatively coupled, electronically coupled, orelectrically coupled.

In general, any quantity of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology or an air interface. A frequency maybe referred to as a carrier or a frequency channel. Each frequency maysupport a single RAT in a given geographic area in order to avoidinterference between wireless networks of different RATs. In some cases,NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (for example, shown as UE 120 aand UE 120 e) may communicate directly using one or more sidelinkchannels (for example, without using a base station 110 as anintermediary to communicate with one another). For example, the UEs 120may communicate using peer-to-peer (P2P) communications,device-to-device (D2D) communications, a vehicle-to-everything (V2X)protocol (for example, which may include a vehicle-to-vehicle (V2V)protocol, a vehicle-to-infrastructure (V2I) protocol, or avehicle-to-pedestrian (V2P) protocol), or a mesh network. In suchexamples, a UE 120 may perform scheduling operations, resource selectionoperations, or other operations described elsewhere herein as beingperformed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, or channels. For example,devices of the wireless network 100 may communicate using one or moreoperating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band invarious documents and articles. A similar nomenclature issue sometimesoccurs in connection with FR2, which is often referred to(interchangeably) as a “millimeter wave” band in documents and articles,despite being different from the extremely high frequency (EHF) band (30GHz-300 GHz) which is identified by the International TelecommunicationsUnion (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics or FR2 characteristics, and thus may effectively extendfeatures of FR1 or FR2 into mid-band frequencies. In addition, higherfrequency bands are currently being explored to extend 5G NR operationbeyond 52.6 GHz. For example, three higher operating bands have beenidentified as frequency range designations FR4a or FR4-1 (52.6 GHz-71GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each ofthese higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,the term “sub-6 GHz,” if used herein, may broadly represent frequenciesthat may be less than 6 GHz, may be within FR1, or may include mid-bandfrequencies. Further, unless specifically stated otherwise, the term“millimeter wave,” if used herein, may broadly represent frequenciesthat may include mid-band frequencies, may be within FR2, FR4, FR4-a orFR4-1, or FR5, or may be within the EHF band. It is contemplated thatthe frequencies included in these operating bands (for example, FR1,FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and techniquesdescribed herein are applicable to those modified frequency ranges.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may receive an indication of an initial downlink bandwidth for the UE;receive, via a master information block (MIB), configuration informationfor a control resource set (CORESET) associated with physical downlinkcontrol channel (PDCCH) monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth; and receive one or more PDCCH messages associatedwith the CORESET based at least in part on at least one of modifying aresource mapping of the CORESET or modifying the initial downlinkbandwidth. Additionally or alternatively, the communication manager 140may perform one or more other operations described herein.

In some aspects, the base station 110 may include a communicationmanager 150. As described in more detail elsewhere herein, thecommunication manager 150 may transmit, to a UE 120, an indication of aninitial downlink bandwidth for the UE; transmit, to the UE via an MIB,configuration information for a CORESET associated with PDCCH monitoringfor initial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and transmit, tothe UE, one or more PDCCH messages associated with the CORESET based atleast in part on indicating an action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth. Additionally oralternatively, the communication manager 150 may perform one or moreother operations described herein.

FIG. 2 is a diagram illustrating an example base station incommunication with a UE in a wireless network in accordance with thepresent disclosure. The base station may correspond to the base station110 of FIG. 1 . Similarly, the UE may correspond to the UE 120 of FIG. 1. The base station 110 may be equipped with a set of antennas 234 athrough 234 t, such as T antennas (T≥1). The UE 120 may be equipped witha set of antennas 252 a through 252 r, such as R antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The UE 120may process (for example, encode and modulate) the data for the UE 120based at least in part on the MCS(s) selected for the UE 120 and mayprovide data symbols for the UE 120. The transmit processor 220 mayprocess system information (for example, for semi-static resourcepartitioning information (SRPI)) and control information (for example,CQI requests, grants, or upper layer signaling) and provide overheadsymbols and control symbols. The transmit processor 220 may generatereference symbols for reference signals (for example, a cell-specificreference signal (CRS) or a demodulation reference signal (DMRS)) andsynchronization signals (for example, a primary synchronization signal(PSS) or a secondary synchronization signal (SSS)). A transmit (TX)multiple-input multiple-output (MIMO) processor 230 may perform spatialprocessing (for example, precoding) on the data symbols, the controlsymbols, the overhead symbols, or the reference symbols, if applicable,and may provide a set of output symbol streams (for example, T outputsymbol streams) to a corresponding set of modems 232 (for example, Tmodems), shown as modems 232 a through 232 t. For example, each outputsymbol stream may be provided to a modulator component (shown as MOD) ofa modem 232. Each modem 232 may use a respective modulator component toprocess a respective output symbol stream (for example, for OFDM) toobtain an output sample stream. Each modem 232 may further use arespective modulator component to process (for example, convert toanalog, amplify, filter, or upconvert) the output sample stream toobtain a downlink signal. The modems 232 a through 232 t may transmit aset of downlink signals (for example, T downlink signals) via acorresponding set of antennas 234 (for example, T antennas), shown asantennas 234 a through 234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 orother base stations 110 and may provide a set of received signals (forexample, R received signals) to a set of modems 254 (for example, Rmodems), shown as modems 254 a through 254 r. For example, each receivedsignal may be provided to a demodulator component (shown as DEMOD) of amodem 254. Each modem 254 may use a respective demodulator component tocondition (for example, filter, amplify, downconvert, or digitize) areceived signal to obtain input samples. Each modem 254 may use ademodulator component to further process the input samples (for example,for OFDM) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from the modems 254, may perform MIMO detection on thereceived symbols if applicable, and may provide detected symbols. Areceive processor 258 may process (for example, demodulate and decode)the detected symbols, may provide decoded data for the UE 120 to a datasink 260, and may provide decoded control information and systeminformation to a controller/processor 280. The term“controller/processor” may refer to one or more controllers, one or moreprocessors, or a combination thereof. A channel processor may determinea reference signal received power (RSRP) parameter, a received signalstrength indicator (RSSI) parameter, a reference signal received quality(RSRQ) parameter, or a CQI parameter, among other examples. In someexamples, one or more components of the UE 120 may be included in ahousing.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the base station 110 via thecommunication unit 294.

One or more antennas (for example, antennas 234 a through 234 t orantennas 252 a through 252 r) may include, or may be included within,one or more antenna panels, one or more antenna groups, one or more setsof antenna elements, or one or more antenna arrays, among otherexamples. An antenna panel, an antenna group, a set of antenna elements,or an antenna array may include one or more antenna elements (within asingle housing or multiple housings), a set of coplanar antennaelements, a set of non-coplanar antenna elements, or one or more antennaelements coupled to one or more transmission or reception components,such as one or more components of FIG. 2 .

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (forexample, for reports that include RSRP, RSSI, RSRQ, or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (for example, forDFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In someexamples, the modem 254 of the UE 120 may include a modulator and ademodulator. In some examples, the UE 120 includes a transceiver. Thetransceiver may include any combination of the antenna(s) 252, themodem(s) 254, the MIMO detector 256, the receive processor 258, thetransmit processor 264, or the TX MIMO processor 266. The transceivermay be used by a processor (for example, the controller/processor 280)and the memory 282 to perform aspects of any of the methods describedherein.

At the base station 110, the uplink signals from UE 120 or other UEs maybe received by the antennas 234, processed by the modem 232 (forexample, a demodulator component, shown as DEMOD, of the modem 232),detected by a MIMO detector 236 if applicable, and further processed bya receive processor 238 to obtain decoded data and control informationsent by the UE 120. The receive processor 238 may provide the decodeddata to a data sink 239 and provide the decoded control information tothe controller/processor 240. The base station 110 may include acommunication unit 244 and may communicate with the network controller130 via the communication unit 244. The base station 110 may include ascheduler 246 to schedule one or more UEs 120 for downlink or uplinkcommunications. In some examples, the modem 232 of the base station 110may include a modulator and a demodulator. In some examples, the basestation 110 includes a transceiver. The transceiver may include anycombination of the antenna(s) 234, the modem(s) 232, the MIMO detector236, the receive processor 238, the transmit processor 220, or the TXMIMO processor 230. The transceiver may be used by a processor (forexample, the controller/processor 240) and the memory 242 to performaspects of any of the methods described herein.

The controller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, or any other component(s) ofFIG. 2 may perform one or more techniques associated with partialCORESET handling, as described in more detail elsewhere herein. Forexample, the controller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 800 ofFIG. 8 , process 900 of FIG. 9 , or other processes as described herein.The memory 242 and the memory 282 may store data and program codes forthe base station 110 and the UE 120, respectively. In some examples, thememory 242 or the memory 282 may include a non-transitorycomputer-readable medium storing one or more instructions (for example,code or program code) for wireless communication. For example, the oneor more instructions, when executed (for example, directly, or aftercompiling, converting, or interpreting) by one or more processors of thebase station 110 or the UE 120, may cause the one or more processors,the UE 120, or the base station 110 to perform or direct operations of,for example, process 800 of FIG. 8 , process 900 of FIG. 9 , or otherprocesses as described herein. In some examples, executing instructionsmay include running the instructions, converting the instructions,compiling the instructions, or interpreting the instructions, amongother examples.

In some aspects, the UE 120 includes means for receiving an indicationof an initial downlink bandwidth for the UE; means for receiving, via anMIB, configuration information for a CORESET associated with PDCCHmonitoring for initial access, wherein the configuration informationindicates a frequency domain resource allocation for the CORESET, andwherein the frequency domain resource allocation for the CORESET is atleast partially outside of the initial downlink bandwidth; or means forreceiving one or more PDCCH messages associated with the CORESET basedat least in part on at least one of modifying a resource mapping of theCORESET or modifying the initial downlink bandwidth. The means for theUE 120 to perform operations described herein may include, for example,one or more of communication manager 140, antenna 252, modem 254, MIMOdetector 256, receive processor 258, transmit processor 264, TX MIMOprocessor 266, controller/processor 280, or memory 282.

In some aspects, the base station 110 includes means for transmitting,to a UE 120, an indication of an initial downlink bandwidth for the UE;means for transmitting, to the UE 120 via an MIB, configurationinformation for a CORESET associated with PDCCH monitoring for initialaccess, wherein the configuration information indicates a frequencydomain resource allocation for the CORESET, and wherein the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth; or means for transmitting, to the UE,one or more PDCCH messages associated with the CORESET based at least inpart on indicating an action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth. The means for thebase station 110 to perform operations described herein may include, forexample, one or more of communication manager 150, transmit processor220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236,receive processor 238, controller/processor 240, memory 242, orscheduler 246.

FIG. 3 is a diagram illustrating an example resource structure 300 forwireless communication, in accordance with the present disclosure.Resource structure 300 shows an example of various groups of resourcesdescribed herein. As shown, resource structure 300 may include asubframe 305. Subframe 305 may include multiple slots 310. Whileresource structure 300 is shown as including 2 slots per subframe, adifferent quantity of slots may be included in a subframe (for example,4 slots, 8 slots, 16 slots, 32 slots, or another quantity of slots). Insome examples, different types of transmission time intervals (TTIs) maybe used, other than subframes or slots. A slot 310 may include multiplesymbols 315, such as 14 symbols per slot.

The potential control region of a slot 310 may be referred to as aCORESET 320 and may be structured to support an efficient use ofresources, such as by flexible configuration or reconfiguration ofresources of the CORESET 320 for one or more PDCCHs or one or morephysical downlink shared channels (PDSCHs). In some examples, theCORESET 320 may occupy the first symbol 315 of a slot 310, the first twosymbols 315 of a slot 310, or the first three symbols 315 of a slot 310.Thus, a CORESET 320 may include multiple resource blocks (RBs) in thefrequency domain, and either one, two, or three symbols 315 in the timedomain. In 5G, a quantity of resources included in the CORESET 320 maybe flexibly configured, such as by using radio resource control (RRC)signaling to indicate a frequency domain region (for example, a quantityof resource blocks) or a time domain region (for example, a quantity ofsymbols) for the CORESET 320.

As illustrated, a symbol 315 that includes CORESET 320 may include oneor more control channel elements (CCEs) 325, shown as two CCEs 325 as anexample, that span a portion of the system bandwidth. A CCE 325 mayinclude downlink control information (DCI) that is used to providecontrol information for wireless communication. A base station maytransmit DCI during multiple CCEs 325 (as shown), where the quantity ofCCEs 325 used for transmission of DCI represents the aggregation level(AL) used by the base station for the transmission of DCI. In FIG. 3 ,an aggregation level of two is shown as an example, corresponding to twoCCEs 325 in a slot 310. In some aspects, different aggregation levelsmay be used, such as 1, 2, 4, 8, 16, or another aggregation level.

Each CCE 325 may include a fixed quantity of resource element groups(REGs) 330, shown as 6 REGs 330, or may include a variable quantity ofREGs 330. In some examples, the quantity of REGs 330 included in a CCE325 may be specified by a REG bundle size. A REG 330 may include oneresource block (RB), which may include 12 resource elements (REs) 335within a symbol 315 (for example, an REG may include 1 RB in thefrequency domain and 1 symbol in the time domain). A resource element335 may occupy one subcarrier in the frequency domain and one OFDMsymbol in the time domain.

A search space may include all possible locations (for example, in timeor frequency) where a PDCCH may be located. A CORESET 320 may includeone or more search spaces, such as a UE-specific search space, agroup-common search space, or a common search space. A search space mayindicate a set of CCE locations where a UE may find PDCCHs that canpotentially be used to transmit control information to the UE. Thepossible locations for a PDCCH may depend on whether the PDCCH is aUE-specific PDCCH (for example, for a single UE) or a group-common PDCCH(for example, for multiple UEs) or an aggregation level being used. Apossible location (for example, in time or frequency) for a PDCCH may bereferred to as a PDCCH candidate, and the set of all possible PDCCHlocations (or PDCCH candidates) at an aggregation level may be referredto as a search space. For example, the set of all possible PDCCHlocations (or all possible PDCCH candidates) for a particular UE may bereferred to as a UE-specific search space. Similarly, the set of allpossible PDCCH locations (or all possible PDCCH candidates) across allUEs may be referred to as a common search space. The set of all possiblePDCCH locations (or all possible PDCCH candidates) for a particulargroup of UEs may be referred to as a group-common search space. One ormore search spaces across aggregation levels may be referred to as asearch space (SS) set.

A CORESET 320 may be interleaved or non-interleaved. An interleavedCORESET 320 may have CCE-to-REG mapping such that adjacent CCEs aremapped to scattered REG bundles in the frequency domain (for example,adjacent CCEs are not mapped to consecutive REG bundles of the CORESET320). A non-interleaved CORESET 320 may have a CCE-to-REG mapping suchthat all CCEs are mapped to consecutive REG bundles (for example, in thefrequency domain) of the CORESET 320.

Increases in carrier frequencies may enable the use of larger antennaarrays and bandwidths by UEs. Additionally, interest in millimeter wavefrequency regimes is increasing, as these bandwidths can accommodatelarger channel bandwidths than non-millimeter wave bandwidths. Bandwidthparts (BWPs), which are subsets of contiguous common physical resourceblocks, may be used to configure active frequencies based on a UE'sneeds and capabilities. As used herein, “bandwidth part” or “BWP” mayrefer to a contiguous set of physical resource blocks (PRBs), where eachPRB includes a set of frequencies corresponding to one or moresubcarriers. A “subcarrier” may refer to a frequency based at least inpart on a “carrier” frequency, and subcarriers may be aggregated toconvey information wirelessly (for example, using OFDM symbols or otherradio frequency symbols). Within a component carrier (CC), differentBWPs may be supported on a band. In a typical case, a UE is expected toreceive and transmit only within the frequency range configured for anactive BWP (for example, rather than the entire frequency range of theband). CORESETs 320 or SS sets may be configured for a BWP. For example,a CORESET 320 may be configured for one or more BWPs configured for aUE.

In some cases, multiple BWPs may be configured for a UE, such as aninitial BWP, one or more dedicated BWPs, or a dormant BWP, among otherexamples. The initial BWP (for example, an initial downlink BWP) may beused for initial access purposes (for example, to be used to access achannel prior to receiving a radio resource control (RRC)configuration). A BWP, from among multiple configured BWPs, activelyutilized by the UE may be referred to as an active BWP. In some cases,the initial BWP may be a default BWP, which the UE may utilize when, forexample, an inactivity timer expires.

In some cases, an initial CORESET may be configured for initial accesspurposes (for example, associated with an initial BWP). For example, aninitial CORESET may be a CORESET associated with PDCCH monitoring forinitial access. In some cases, an initial CORESET may be associated withmonitoring for or receiving a system information block 1 (SIB1) (asdefined, or otherwise fixed, by a wireless communication standard). Theinitial CORESET may be a Type0-PDCCH CORESET (for example, as defined,or otherwise fixed, by a wireless communication standard, such as the3GPP) and may be referred to as a “CORESET 0” or a “CORESET zero.” Forexample, the initial CORESET may be configured for a cell prior to a UEreceiving any RRC configuration. In some cases, the initial CORESET maybe configured via a master information block (MIB) (for example, via aPDCCH-ConfigSIB1 information element, a controlResourceSetZeroinformation element, or a searchSpaceZero information element in theMIB, as defined, or otherwise fixed, by a wireless communicationstandard, such as the 3GPP). An MIB may be broadcast periodically by abase station. The MIB may indicate parameters (such as a system framenumber, a subcarrier spacing (SCS) for a system information block (SIB),a PDCCH configuration for the SIB, among other examples) to enable UEsin the network to receive the SIB for initial access for a cellsupported by the base station. The SIB may be a SIB1, which refers to aSIB that carries information relevant when evaluating if a UE is allowedto access a cell, defines the scheduling of other system information, orprovides RRC information that is common for all UEs in the cell, amongother examples. The MIB and SIB1 may be referred to as minimum systeminformation (MSI). In some cases, SIB1 may be referred to as remainingminimum system information (RMSI).

In some cases, a frequency domain resource allocation for an initialCORESET (a CORESET 0) may be defined with reference to a synchronizationsignal block (SSB) (for example, with reference to a lowest frequency ofthe SSB). For example, some CORESETs may be defined with reference to acommon reference point for resource block grids, which may be referredto as a “Point A,” an “absolute frequency point A,” or a “common RB(CRB) 0.” However, the common reference point may be indicated to the UEvia RRC signaling. Therefore, for a configuration of the initialCORESET, the UE may be, in some cases, only aware of (or receive) an SSBtransmitted by a base station and the MIB transmitted by the basestation. Therefore, a frequency domain resource allocation for aninitial CORESET (a CORESET 0) may be defined with reference to anassociated SSB (for example, that may be multiplexed with the initialCORESET, as explained in more detail elsewhere herein).

FIG. 4 is a diagram illustrating an example of a synchronization signal(SS) hierarchy 400, in accordance with the present disclosure. As shownin FIG. 4 , the SS hierarchy may include an SS burst set 405, which mayinclude multiple SS bursts 410, shown as SS burst 0 through SS burstN−1, where Nis a maximum quantity of repetitions of the SS burst 410that may be transmitted by the base station. As further shown, each SSburst 410 may include one or more SS blocks (SSBs) 415, shown as SSB 0through SSB M−1, where M is a maximum quantity of SSBs 415 that can becarried by an SS burst 410. In some examples, different SSBs 415 may bebeam-formed differently (for example, transmitted using differentbeams), and may be used for cell search, cell acquisition, beammanagement, or beam selection (for example, as part of an initialnetwork access procedure). An SS burst set 405 may be periodicallytransmitted by a wireless node (for example, a base station 110), suchas every X milliseconds, as shown in FIG. 4 . In some examples, an SSburst set 405 may have a fixed or dynamic length, shown as Ymilliseconds in FIG. 4 . In some cases, an SS burst set 405 or an SSburst 410 may be referred to as a discovery reference signal (DRS)transmission window or an SSB measurement time configuration (SMTC)window.

In some examples, an SSB 415 may include resources that carry a primarysynchronization signal (PSS) 420, a secondary synchronization signal(SSS) 425, or a physical broadcast channel (PBCH) 430. In some examples,multiple SSBs 415 are included in an SS burst 410 (for example, withtransmission on different beams), and the PSS 420, the SSS 425, or thePBCH 430 may be the same across each SSB 415 of the SS burst 410. Insome examples, a single SSB 415 may be included in an SS burst 410. Insome examples, the SSB 415 may be at least four symbols (for example,OFDM symbols) in length, where each symbol carries one or more of thePSS 420 (for example, occupying one symbol), the SSS 425 (for example,occupying one symbol), or the PBCH 430 (for example, occupying twosymbols). In some cases, an SSB 415 may be referred to as an SS/PBCHblock.

In some examples, the symbols of an SSB 415 are consecutive, as shown inFIG. 4 . In some other examples, the symbols of an SSB 415 arenon-consecutive. Similarly, in some examples, one or more SSBs 415 ofthe SS burst 410 may be transmitted in consecutive radio resources (forexample, consecutive symbols) during one or more slots. Additionally oralternatively, one or more SSBs 415 of the SS burst 410 may betransmitted in non-consecutive radio resources.

In some examples, the SS bursts 410 may have a burst period, and theSSBs 415 of the SS burst 410 may be transmitted by a wireless node (forexample, a base station 110) in accordance with the burst period. Insuch examples, the SSBs 415 may be repeated during each SS burst 410. Insome examples, the SS burst set 405 may have a burst set periodicity,whereby the SS bursts 410 of the SS burst set 405 are transmitted by thewireless node in accordance with the fixed burst set periodicity. Inother words, the SS bursts 410 may be repeated during each SS burst set405.

In some examples, an SSB 415 may include an SSB index, which maycorrespond to a beam used to carry the SSB 415. A UE 120 may monitor foror measure SSBs 415 using different receive (Rx) beams during an initialnetwork access procedure or a cell search procedure, among otherexamples. Based at least in part on the monitoring or measuring, the UE120 may indicate one or more SSBs 415 with a best signal parameter (forexample, an RSRP parameter) to a base station 110. The base station 110and the UE 120 may use the one or more indicated SSBs 415 to select oneor more beams to be used for communication between the base station 110and the UE 120 (for example, for a random access channel (RACH)procedure). Additionally or alternatively, the UE 120 may use the SSB415 or the SSB index to determine a cell timing for a cell via which theSSB 415 is received (for example, for a serving cell).

In some cases, an SSB may be associated with a CORESET (for example, aCORESET 0). For example, an SSB may serve as a source reference signalthat provides beam information for the CORESET, such as quasico-location (QCL) assumption information, among other examples, to beused by the UE to decode the CORESET (for example, to decode ademodulation reference signal (DMRS) included in the CORESET). The SSBmay be multiplexed (for example, time division multiplexed or frequencydivision multiplexed) with the CORESET. An MIB (for example, thepdcch-ConfigSIB1 information element or the controlResourceSetZeroinformation element) may indicate a multiplexing pattern for an SSB anda CORESET (for example, an initial CORESET or a CORESET 0).

FIG. 5 is a diagram illustrating an example of multiplexing patterns 500for SSBs and CORESETs, in accordance with the present disclosure. Asdescribed elsewhere herein, an SSB and a CORESET (for example, a CORESET0) may be multiplexed in the time domain or the frequency domain. Forexample, the SSB and the CORESET may be time division multiplexed(TDM'ed) or frequency division multiplexed (FDM'ed). A multiplexingpattern (for example, a time division multiplex (TDM) pattern or afrequency division multiplex (FDM) pattern) for the SSB and the CORESETmay be indicated in configuration information for the CORESET (forexample, in an MIB). One or more multiplexing patterns may be defined,or otherwise fixed, by a wireless communication standard, such as the3GPP.

For example, an SSB and an initial CORESET (a CORESET 0) may bemultiplexed to enable the SSB to serve as a reference point for defininga frequency domain resource allocation for the initial CORESET, asdescribed above. Additionally or alternatively, an SSB and an initialCORESET may be multiplexed so that the SSB may serve as a sourcereference signal for providing beam information or QCL information forthe CORESET.

For example, a first multiplexing pattern 510 may be a TDM pattern. Forexample, as shown in FIG. 5 , the SSB and the CORESET may be multiplexedin the time domain. In some cases, a reference point for defining thefrequency domain resource allocation for the CORESET may be an RB of theSSB associated with a highest index value or an RB of the SSB associatedwith a lowest index value. In some cases, a starting RB (or CCE) of theCORESET may be offset, in the frequency domain, from the RB of the SSBassociated with the highest index value or the RB of the SSB associatedwith the lowest index value. The first multiplexing pattern 510 may beused when an SCS of the SSB and an SCS of the CORESET are the same ordifferent. For example, the first multiplexing pattern 510 may be usedwhen the SCS of the SSB is 120 kilohertz (kHz) and the SCS of theCORESET is 120 kHZ, when the SCS of the SSB is 240 kHz and the SCS ofthe CORESET is 60 kHZ, or when the SCS of the SSB is 240 kHz and the SCSof the CORESET is 120 kHZ, among other examples.

A second multiplexing pattern 520 may be a combination of a TDM patternand an FDM pattern. For example, the SSB and the CORESET may bemultiplexed in the time domain and the frequency domain. As shown inFIG. 5 , the frequency domain resources used by the SSB and the CORESETmay be contiguous (for example, the RBs allocated for the SSB may becontiguous with the RBs allocated for the CORESET), but the SSB and theCORESET may occupy different symbols in the time domain. In some cases,a starting RB (or CCE) of the CORESET may be offset, in the frequencydomain, from the RB of the SSB associated with the highest index valueor the RB of the SSB associated with the lowest index value (as shown inFIG. 5 ). The second multiplexing pattern 520 may be used when the SSBand the CORESET are associated with different SCSs.

A third multiplexing pattern 530 may be an FDM pattern. For example, theSSB and the CORESET may be multiplexed in the frequency domain. In somecases, a reference point for defining the frequency domain resourceallocation for the CORESET may be an RB of the SSB associated with ahighest index value or an RB of the SSB associated with a lowest indexvalue. As shown in FIG. 5 , the frequency domain resources used by theSSB and the CORESET may be contiguous (for example, the RBs allocatedfor the SSB may be contiguous with the RBs allocated for the CORESET)and the SSB and the CORESET may occupy at least one common symbol in thetime domain. The third multiplexing pattern 530 may be used when the SCSof the SSB is the same as the SCS of the CORESET.

A multiplexing pattern to be applied (for example, among the firstmultiplexing pattern 510, the second multiplexing pattern 520, and thethird multiplexing pattern 530) for a CORESET and SSB may be indicatedby a base station to a UE via configuration information, such as an RRCconfiguration, system information, or an MIB, among other examples. Forexample, for an initial CORESET (a CORESET 0) the multiplexing patternto be applied may be indicated in an MIB (for example, in apdcch-ConfigSIB1 information element or a controlResourceSetZeroinformation element of the MIB). The MIB may indicate a frequency offset(for example, from an RB of the SSB to identify a starting RB of theinitial CORESET), a quantity of RBs associated with the initial CORESET,and a quantity of symbols associated with the CORESET. For example, theinitial CORESET (CORESET 0) may include 1, 2, or 3 symbols, among otherexamples. The initial CORESET may include 24 RBs, 48 RBs, or 96 RBs,among other examples.

In some cases, a configuration of a CORESET 0 and a multiplexing patternused for the CORESET 0 and an SSB may result in a frequency domainresource allocation for the CORESET 0 and the SSB exceeding a bandwidthassociated with a UE (for example, an active or an initial downlink BWPor a maximum UE bandwidth). For example, a quantity of RBs allocated forthe CORESET 0 and the SSB may exceed a quantity of RBs that can besupported or received (in accordance with the bandwidth associated withthe UE) by the UE, as depicted and described in more detail inconnection with FIG. 6 .

FIG. 6 is a diagram illustrating an example of a partial CORESET 600, inaccordance with the present disclosure. “Partial CORESET” may refer to aCORESET, configured at a UE, that is associated with a frequency domainresource allocation that is at least partially outside of a bandwidth(for example, an initial downlink BWP or a maximum UE bandwidth) of theUE. For example, in some cases, a UE may be associated with a smallerbandwidth because of a capability of the UE.

For example, in some cases, a base station may serve different UEs ofdifferent categories or different UEs that support differentcapabilities. For example, the base station may serve a first categoryof UEs that have a less advanced capability (such as a lower capabilityor a reduced capability) and a second category of UEs that have a moreadvanced capability (for example, a higher capability). A UE of thefirst category may have a reduced feature set compared to UEs of thesecond category, and may be referred to as a reduced capability (RedCap)UE, a low tier UE, or an NR-Lite UE, among other examples. A UE of thefirst category may be, for example, an MTC UE, an eMTC UE, or an IoT UE,as described above in connection with FIG. 1 . A UE of the secondcategory may have an advanced feature set compared to UEs of the secondcategory, and may be referred to as a baseline UE, a high tier UE, an NRUE, or a premium UE, among other examples. In some aspects, a UE of thefirst category has capabilities that satisfy requirements of a first(earlier) wireless communication standard but not a second (later)wireless communication standard, while a UE of the second category hascapabilities that satisfy requirements of the second (later) wirelesscommunication standard (and also the first wireless communicationstandard, in some cases).

For example, UEs of the first category may support a lower maximummodulation and coding scheme (MCS) than UEs of the second category (suchas quadrature phase shift keying (QPSK) as compared to 256-quadratureamplitude modulation (QAM)), may support a lower maximum transmit powerthan UEs of the second category, may have a less advanced beamformingcapability than UEs of the second category (for example, may not becapable of forming as many beams as UEs of the second category), mayrequire a longer processing time than UEs of the second category, mayinclude less hardware than UEs of the second category (for example,fewer antennas, fewer transmit antennas, or fewer receive antennas), ormay not be capable of communicating on as wide of a maximum BWP as UEsof the second category, among other examples. Additionally oralternatively, UEs of the second category may be capable ofcommunicating using a shortened transmission time interval (TTI) (forexample, a slot length of 1 ms or less, 0.5 ms, 0.25 ms, 0.125 ms, or0.0625 ms, depending on a SCS), and UEs of the first category may not becapable of communicating using the shortened TTI.

Therefore, UEs of the first category (for example, reduced capabilityUEs) may be configured with an initial downlink BWP (for example, forinitial access purposes) that is different than an initial downlink BWPfor UEs of the second category. For example, the initial downlink BWPfor UEs of the second category may be larger than the initial downlinkBWP for UEs of the first category. For example, for initial access, a UEbandwidth 610 (or BWP) for a UE of the first category (for example, areduced capability UE) may be limited to, or may not exceed, 100megahertz (MHz).

As shown in FIG. 6 , a CORESET 620 may be configured for the UE. Forexample, the UE may receive a configuration for the CORESET 620 via anMIB. The CORESET 620 may be an initial CORESET or a CORESET 0. TheCORESET 620 may be multiplexed with an SSB. For example, as shown inFIG. 6 , the CORESET 620 may multiplexed with an SSB in accordance withthe third multiplexing pattern 530. FIG. 6 depicts an exampleconfiguration for the CORESET 620 that includes two PDCCH candidates(for example PDCCH candidate 1 and PDCCH candidate 2), each PDCCHcandidate having an aggregation level (AL) of 4 (for example, each PDCCHcandidate is associated with 4 CCEs). As shown in FIG. 6 , the CORESETmay be associated with interleaved CCE-to-REG mapping (for example,consecutive CCE indices may be mapped to non-consecutive REGs).

As shown in FIG. 6 , a portion of the frequency domain resourceallocation (for example, one or more CCEs) of the CORESET may be outsideof the UE bandwidth 610 of a UE (for example, a reduced capability UE).For example, the UE bandwidth 610 may be associated with a quantity ofRBs or a quantity of MHz (for example, for a 100 MHz maximum bandwidth,the quantity of RBs may be 66). A frequency range or a quantity of RBsassociated with the SSB and the CORESET 620 may exceed the quantity ofRBs or a quantity of MHz associated with the UE bandwidth 610. Forexample, some CORESET 0 configuration may result in an SSB/CORESETconfiguration that is larger, in the frequency domain, than the UEbandwidth 610. While FIG. 6 shows an example, of a CORESET configurationthat is associated with 2 PDCCH candidates, an aggregation level of 4,and the third multiplexing pattern 530, other CORESET configurations maysimilarly result in a partial CORESET, such as CORESET configurationsthat use the second multiplexing pattern 520, among other examples.

Because the portion of the frequency domain resource allocation (forexample, one or more CCEs) of the CORESET may be outside of the UEbandwidth 610, the UE may be unable to receive or decode CCEs or RBs 630of the CORESET 620. For example, in the example depicted in FIG. 6 , theUE may be unable to receive CCEs with index values of 1 and 3(associated with the PDCCH candidate 1) and 5 and 7 (associated with thePDCCH candidate 2). The UE may receive and decode CCEs with index valuesof 0 and 2 (associated with the PDCCH candidate 1) and 4 and 6(associated with the PDCCH candidate 2) because the CCEs are within theUE bandwidth 610. Because the UE may be unable to receive a portion ofthe CORESET 620, a communication performance of the UE may be degraded.For example, an aggregation level of the PDCCH candidates associatedwith the CORESET 620 may be reduced (for example, to an aggregationlevel of 2 in the example shown in FIG. 6 ). The reduced aggregationlevel may cause a degradation in the communication performance of theUE.

Various aspects relate generally to partial CORESET handling. Someaspects more specifically relate to receiving, by a UE, PDCCH messagesassociated with a partial CORESET based at least in part on modifying aresource mapping of the partial CORESET or modifying an initial downlinkbandwidth of the UE. For example, in some aspects, the UE may modify aCCE-to-REG mapping using a quantity of available RBs associated with theinitial downlink bandwidth. In some aspects, the UE may modify aCCE-to-REG mapping type of the partial CORESET to a non-interleavingmapping type. In some other aspects, the UE may modify a frequency rangeassociated with the initial downlink bandwidth to include the frequencydomain resource allocation for the partial CORESET based at least inpart on receiving an SSB (for example, after receiving the SSB).

In some aspects, the UE may receive the PDCCH messages associated with apartial CORESET based at least in part on identifying a starting RB ofthe partial CORESET (for example, when the starting RB is outside of theinitial downlink bandwidth of the UE). The UE may identify the startingRB based at least in part on reducing a quantity of resource blocksassociated with the frequency domain resource allocation for the CORESETbased at least in part on a quantity of available resource blocks in theinitial downlink bandwidth. In some aspects, the UE may identify thestarting RB based at least in part on using common resource block indexvalues (rather than RB index values associated with the initial downlinkbandwidth) and a resource block offset indicated by configurationinformation for the partial CORESET. In some other aspects, the UE mayidentify the starting RB based at least in part on virtually extendingresource block indices associated with the initial downlink bandwidth(for example, by extending index value associated with the initialdownlink bandwidth to negative values or values that exceed theconfigured index values for the initial downlink bandwidth).

In some aspects, the UE may receive an indication of an action to beperformed by the UE when the frequency domain resource allocation for aCORESET is at least partially outside of the initial downlink bandwidth(for example, when the CORESET is a partial CORESET). The UE may receivethe indication of the action to be performed via a CORESET zeroconfiguration (for example, the controlResourceSetZero informationelement) included in a PDCCH configuration (for example, in thepdcch-ConfigSIB1 information element) indicated by an MIB thatconfigures the CORESET, via the MIB that configures the CORESET, via asystem information block (SIB), or via dedicated signaling, among otherexamples.

Particular aspects of the subject matter described in this disclosurecan be implemented to realize one or more of the following potentialadvantages. In some examples, the described techniques can be used tomaintain an aggregation level of PDCCH candidates of a CORESET when afrequency domain resource allocation for the CORESET is at leastpartially outside of an initial downlink bandwidth of a UE (for example,when the CORESET is a partial CORESET). Maintaining the aggregationlevel of the PDCCH candidate(s) may improve communication performanceassociated with receiving PDCCH messages associated with the CORESET. Insome aspects, the described techniques can be used to maintain aquantity of PDCCH candidates associated with the CORESET. Maintainingthe quantity of PDCCH candidates may improve a PDCCH capacity associatedwith receiving PDCCH messages associated with the CORESET. In someaspects, the described techniques can be used to remove ambiguityassociated with a starting frequency domain resource (for example, astarting RB) of a CORESET when the starting RB is outside of the initialdownlink bandwidth of the UE. This may enable the UE to map resources(for example, RBs or CCEs) to the CORESET, monitor the CORESET (andassociated search space(s)), and receive one or more PDCCH messagesassociated with the CORESET.

FIGS. 7A and 7B are diagrams illustrating an example associated withpartial CORESET handling 700, in accordance with the present disclosure.As shown in FIG. 7A, a base station 110 and a UE 120 may communicatewith one another in a wireless network, such as the wireless network100. In some aspects, the UE 120 may be a reduced capability UE. Forexample, the UE 120 may be associated with the first category of UEsdescribed elsewhere herein.

In a first operation 705, the base station 110 may transmit, and the UE120 may receive, an indication of an initial downlink bandwidth.“Initial downlink bandwidth” may refer to a BWP or a bandwidth that isto be used by the UE 120 for initial access purposes. “Initial access”may refer to a communication state between the UE 120 and the basestation 110 that occurs prior to the UE 120 establishing a connection,such as an RRC connection, with the base station 110. The initialdownlink bandwidth may be an initial downlink BWP that is configured(for example, via an MIB or other signaling) for the UE 120 to be usedfor initial access purposes (for example, for acquiring a channel or forperforming random access channel procedures). In some aspects, theinitial downlink bandwidth may be a maximum bandwidth that the UE 120may use for initial access purposes (for example, as indicated by thebase station 110, as determined by the UE 120 based at least in part ona configuration of the UE 120, or as defined (or otherwise fixed) by awireless communication standard). In some aspects, the initial downlinkbandwidth may be associated with reduced capability UEs (or UEs includedin the first category of UEs described elsewhere herein). For example, afirst initial downlink BWP may be configured (for example, by the basestation 110) for reduced capability UEs (or for UEs included in thefirst category of UEs) and a second initial downlink BWP may beconfigured (for example, by the base station 110) for UEs included inthe second category of UEs described elsewhere herein. The first initialdownlink BWP may be associated with less radio resources (for example,less frequency domain resources or less time domain resources) that thesecond initial downlink BWP.

For example, the initial downlink bandwidth for reduced capability UEs(or UEs included in the first category of UEs) may be limited in afrequency range to reduce a complexity associated with initial accessprocedures for reduced capability UEs. For example, the initial downlinkbandwidth may be limited to a size of 100 MHz, among other examples. Asdescribed elsewhere herein, the size of the initial downlink bandwidthmay result in a portion of a CORESET (for example, an initial CORESET ora CORESET 0) being configured outside of the initial downlink bandwidth.For example, as depicted and described in connection with FIG. 6 , asize of the initial downlink bandwidth may result one or more RBs orCCEs of the CORESET 0 being mapped to frequency domain resources thatare outside of the initial downlink bandwidth, resulting in a partialCORESET being configured.

In a second operation 710, the base station 110 may transmit, and the UE120 may receive, configuration information. For example, the basestation 110 may transmit (broadcast), the UE 120 may receive, an MIBthat carries the configuration information (for example, in a PDCCHconfiguration indicated by the MIB). The configuration information maybe associated with a CORESET that is associated PDCCH monitoring forinitial access. For example, the configuration information may indicatea configuration for an initial CORESET or a CORESET 0 (for example, in acontrolResourceSetZero information element). The configurationinformation may indicate a multiplexing pattern associated with theCORESET 0, a quantity of symbols associated with the CORESET 0, aquantity of RBs associated with the CORESET 0, or a frequency offsetassociated with the CORESET 0, among other examples.

For example, the controlResourceSetZero information element may indicatean index value that corresponds to a configuration table. Theconfiguration table may include the multiplexing pattern associated withthe CORESET 0, the quantity of symbols associated with the CORESET 0,the quantity of RBs associated with the CORESET 0, or the frequencyoffset associated with the CORESET 0, among other examples. Theconfiguration tables may be defined, or otherwise fixed, by a wirelesscommunication standard (such as one or more configuration tablesincluded in 3GPP Technical Specification 38.213). Because theconfiguration information may be transmitted via the MIB, theconfiguration for the CORESET 0 may be common for all UEs within a cellassociated with the base station 110 (for example, for all reducedcapability UEs within the cell associated with the base station 110). Inother words, because the configuration information may be transmitted(for example, broadcast) via the MIB, the base station 110 may be unableto customize or alter the configuration for the CORESET 0 to ensure thatthe CORESET 0 is entirely included in the initial downlink bandwidth ofthe UE 120.

In some aspects, the indication of the initial downlink bandwidth(transmitted in the first operation 705) may be included in the MIB(transmitted in the second operation 710). In other words, the firstoperation 705 and the second operation 710 may be a single transmission(for example, the same MIB may transmit information described above inconnection with the first operation 705 and the second operation 710).In some other aspects, the indication of the initial downlink bandwidth(transmitted in the first operation 705) may be included in a separatesignal from the MIB (transmitted in the second operation 710).

In a third operation 715, the base station 110 may transmit, and the UE120 may receive, an indication of an action to be performed by UEs 120to handle partial CORESETs. For example, the base station 110 maytransmit, and the UE 120 may receive, an indication of an action to beperformed by UEs 120 when the frequency domain resource allocation for aCORESET is at least partially outside of an initial downlink bandwidth.The third operation 715 may be an optional operation, as indicated bythe dashed arrow in FIG. 7A. For example, in some aspects, the action tobe performed by UEs 120 to handle partial CORESETs may be based at leaston one or more preconfigured rules (for example, rules defined, orotherwise fixed, by a wireless communication standard, such as the3GPP). Therefore, the action to be performed by UEs 120 to handlepartial CORESETs may be specified (for example, by the wirelesscommunication standard) and may not need to be indicated by the basestation 110.

The base station 110 may transmit the indication of the action to beperformed by UEs 120 to handle partial CORESETs via an MIB (for example,the MIB transmitted in the second operation 710). For example, the basestation 110 may transmit the indication of the action to be performed byUEs 120 to handle partial CORESETs via a CORESET zero configuration (acontrolResourceSetZero information element) included in a PDCCHconfiguration (a pdcch-ConfigSIB1 information element) indicated by theMIB. For example, a bit (for example, a most significant bit (MSB)) ofthe CORESET zero configuration may be used to indicate the action to beperformed by UEs 120 to handle partial CORESETs. In some other aspects,the base station 110 may transmit the indication of the action to beperformed by UEs 120 to handle partial CORESETs via another bit of theMIB (for example, a bit that was previously reserved for future purposesas defined, or otherwise fixed, by a wireless communication standard).In some other aspects, the base station 110 may transmit the indicationof the action to be performed by UEs 120 to handle partial CORESETs viaa SIB, such as SIB1 (as defined by a wireless communication standard) oranother SIB. In some other aspects, the base station 110 may transmitthe indication of the action to be performed by UEs 120 to handlepartial CORESETs via dedicated signaling, such as RRC signaling, mediumaccess control (MAC) signaling, or downlink control information (DCI)signaling, among other examples (for example, for cases in which apartial CORESET is configured for the UE 120 after an initial accessstage).

The action to be performed by UEs 120 to handle partial CORESETs mayinclude refraining from receiving CCEs or RBs of the CORESET that areoutside of the initial downlink bandwidth, modifying the resourcemapping of the CORESET, or modifying the initial downlink bandwidth,among other examples. For example, the action to be performed by UEs 120to handle partial CORESETs may include modifying the resource mappingincludes modifying the CCE-to-REG mapping of the CORESET. In someaspects, the action to be performed by UEs 120 to handle partialCORESETs may include modifying a mapping type of the CCE-to-REG mappingof the CORESET between a non-interleaving mapping type and aninterleaving mapping type. In some other aspects, the action to beperformed by UEs 120 to handle partial CORESETs may include shifting afrequency range of the initial downlink bandwidth to include thefrequency domain resource allocation of the CORESET (for example, aftersuccessfully receiving and decoding an SSB associated with the CORESET).

In some aspects, the action to be performed by UEs 120 to handle partialCORESETs may include an action to identify a starting RB of the CORESET.For example, when a portion of the frequency domain resource allocationof the CORESET is outside of the initial downlink bandwidth, a startingRB (for example, an RB associated with a lowest index value or an indexvalue of 0) may be located outside of the initial downlink bandwidth. Insome cases, the UE 120 may use indexing that is associated with theinitial downlink bandwidth. For example, RBs may be indexed, starting atan index value of zero, at a first RB of the initial downlink bandwidthand the indexing of RBs may stop at a last RB of the initial downlinkbandwidth. Therefore, when the starting RB of the CORESET is outside ofthe initial downlink bandwidth, the UE 120 may be unable to mapresources for the CORESET or identify a location of the CORESET becausethe starting RB of the CORESET is not given index value associated withthe initial downlink bandwidth. Therefore, in some aspects, the actionto be performed by UEs 120 to handle partial CORESETs may include anaction to identify the starting RB of the CORESET. The action to beperformed to identify the starting RB of the CORESET may be specified(for example, in a wireless communication standard) or indicated by thebase station 110, in a similar manner as described elsewhere herein. Theaction(s) to be performed by UEs 120 to handle partial CORESETs areexplained in more detail elsewhere herein.

In a fourth operation 720, the UE 120 may identify that the CORESET (forexample, configured by the configuration information or the MIB in thesecond operation 710) is at least partially outside of the initialdownlink bandwidth of the UE 120 (as described in connection with thefirst operation 705). For example, the frequency domain resourceallocation for the CORESET may be at least partially outside of theinitial downlink bandwidth. The UE 120 may identify that the CORESET isa partial CORESET based at least in part on identifying that thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth of the UE 120. TheUE 120 may identify that the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth based at least in part on the configuration information. Forexample, the UE 120 may perform resource mapping to identify thefrequency domain resource allocation for the CORESET based at least inpart on information indicated in the configuration information (such asin the MIB) and based at least in part on one or more configurationtables (for example, that are defined, or otherwise fixed, by a wirelesscommunication standard). Based at least in part on performing theresource mapping (or on identifying the starting RB of the CORESET asdescribed in more detail elsewhere herein), the UE 120 may identify thefrequency domain resource allocation for the CORESET. If the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth of the UE 120, then the UE 120 maydetermine that one or more actions should be performed to handle thepartial CORESET.

In a fifth operation 725, the UE 120 may identify a starting RB of theCORESET. For example, the UE 120 may identify the starting RB of theCORESET based at least in part on the configuration information. Asdescribed above, “starting RB” may refer to an RB associated with theCORESET with a lowest index value or an index value of 0. For example,the configuration information may indicate a frequency offset associatedwith the CORESET that indicates the starting RB of the CORESET withrespect to a first or last RB of an associated SSB (for example, asindicated in the configuration table(s) of 3GPP Technical Specification38.213). The frequency offset may indicate a quantity of RBs from thefirst or last RB of an associated SSB (a multiplexed SSB) to indicatethe starting RB of the CORESET. In some aspects, a value of thefrequency offset may result in the starting RB of the CORESET beingoutside of the initial downlink bandwidth of the UE 120.

In some aspects, the UE 120 may use RB indices that are associated withthe initial downlink bandwidth. For example, index values may be mapped,starting from a first RB of the initial downlink bandwidth, and endingat a last RB of the initial downlink bandwidth. Therefore, when thestarting RB of the CORESET is outside of the initial downlink bandwidth,the UE 120 may be unable to determine an RB that should be mapped to thefirst RB of the CORESET (for example, because there may be no indexvalue associated with that RB that is outside of the initial downlinkbandwidth).

In some aspects, in the fifth operation 725 to identify the starting RBof the CORESET, the UE 120 may reduce a quantity of RBs associated withthe frequency domain resource allocation for the CORESET based at leastin part on a quantity of available RBs, or available CCEs, in theinitial downlink bandwidth. “Available RBs” or “available resourceblocks” may refer to RBs that can be used to receive the CORESET withinthe initial downlink bandwidth. Similarly, “available CCEs” may refer toCCEs that can be used to receive the CORESET within the initial downlinkbandwidth. For example, in some cases, the available RBs may be RBsoriginally allocated for the CORESET minus a quantity of RBs that areoutside of the initial downlink bandwidth as originally configured. Insome aspects, the available RBs may be a quantity of RBs in the initialdownlink bandwidth minus a quantity of RBs (or a portion of the quantityof RBs) allocated to an SSB that is multiplexed with the CORESET. The UE120 may determine that the quantity of RBs associated with the CORESETis the quantity of available RBs. For example, if the configurationinformation indicates that the CORESET is associated with 48 RBs, butonly 24 RBs are within the initial downlink bandwidth, then the UE 120may determine that the CORESET is associated with 24 RBs (rather than 48RBs). The UE 120 may perform resource mapping based at least in part onother information indicated by the configuration information, based atleast in part on the reduced quantity of RBs, or based at least in parton one or more configuration tables, to identify the starting RB of theCORESET. For example, by reducing the quantity of RBs associated withthe CORESET as described herein, the UE 120 may ensure that the startingRB of the CORESET is included within the initial downlink bandwidth.

In some aspects, in the fifth operation 725 to identify the starting RBof the CORESET, the UE 120 may use common resource block index valuesand a resource block offset indicated by the configuration information.“Common resource block index values” or “common RB index values” mayrefer to index values that are defined from a first RB of a carrierbandwidth, rather than from a first RB of the initial downlink bandwidth(which may be a portion of the carrier bandwidth). For example, thefirst RB of the carrier bandwidth may be referred to as common RB (CRB)zero, as CRB0, or as Point A, among other examples. Common RB indexvalues may define index values for all RBs included in the carrierbandwidth, starting from the CRB0 or the Point A. Therefore, rather thanusing index values associated with the initial downlink bandwidth (forexample, index values associated with an initial downlink BWP of the UE120), the UE 120 may use the common RB index values to identify thestarting RB of the CORESET. This may enable the UE 120 to map thestarting RB of the CORESET to an RB identified by a common RB indexvalue when that RB may not have an index value associated with theinitial downlink bandwidth. This enables the UE 120 to identify thestarting RB of the CORESET when the starting RB is outside of theinitial downlink bandwidth.

In some aspects, in the fifth operation 725 to identify the starting RBof the CORESET, the UE 120 may virtually extend RB indices associatedwith the initial downlink bandwidth. “Virtually” extending RB indicesmay refer to the UE 120 assigning (for example, autonomously or withoutreceiving an indication to do so from the base station 110) index valuesto RBs that do not otherwise have an RB index value associated with theinitial downlink bandwidth. For example, the UE 120 may assign negativeindex values (for example below 0) may be extend index values to RBsoutside of the initial downlink bandwidth. For example, if the initialdownlink bandwidth includes RBs with index values from 0 to 50, then theUE 120 may assign negative index values (for example, −1, −2, or −3) toRBs that have a frequency lower than the frequency of the RB associatedwith the index value of 0. Similarly, the UE 120 may assign index valuesgreater than 50 (for example, 51, 52, or 53) to RBs that have afrequency greater than the frequency of the RB associated with the indexvalue of 50. In this way, the UE 120 may be enabled to identify indexvalue for RBs that are outside of the initial downlink bandwidth.Therefore, the UE 120 may be enabled to identify an index value for thestarting RB of the CORESET and may appropriately map the RBs of theCORESET to RBs of the carrier bandwidth or the initial downlinkbandwidth.

Identifying the starting RB of the CORESET may enable the UE 120 to mapRBs of the carrier bandwidth or the initial downlink bandwidth to theCORESET. This may enable the UE 120 to monitor the RBs associated withthe CORESET (for example, to monitor search spaces or PDCCH candidatesassociated with the CORESET). Monitoring the CORESET or the associatedsearch spaces may enable the UE 120 to receive PDCCH messages, asexplained in more detail elsewhere herein.

In a sixth operation 730, the UE 120 may perform an action for partialCORESET handling. For example, the UE 120 may perform an actionassociated with RBs or CCEs of the CORESET that are outside of theinitial downlink bandwidth of the UE 120. In some aspects, the actionmay include refraining from monitoring the RBs or CCEs of the CORESETthat are outside of the initial downlink bandwidth. For example, the UE120 may not be expected to monitor, or receive PDCCH messages in, theRBs or CCEs of the CORESET that are outside of the initial downlinkbandwidth. Refraining from monitoring, or refraining from receivingPDCCH messages in, the RBs or CCEs of the CORESET that are outside ofthe initial downlink bandwidth may reduce a complexity associated withhandling partial CORESETs. Reducing the complexity may be beneficialbecause the UE 120 may be a reduced capability UE, as describedelsewhere herein. Moreover, refraining from monitoring, or refrainingfrom receiving PDCCH messages in, the RBs or CCEs of the CORESET thatare outside of the initial downlink bandwidth may ensure that a quantityof PDCCH candidates is maintained (for example, because a resourcemapping is not modified), resulting in a PDCCH capacity of the CORESETbeing maintained.

In some aspects, the sixth operation 730 may include the UE 120modifying a resource mapping of the CORESET. For example, the UE 120 maymodify a CCE-to-REG mapping of the CORESET. In some aspects, modifyingthe resource mapping of the CORESET may include performing CCE-to-REGmapping using a quantity of available resource blocks, or a quantity ofavailable CCEs, in the initial downlink bandwidth. For example, the UE120 may identify the quantity of available RBs, or a quantity ofavailable CCEs, in the initial downlink bandwidth for the CORESET, asexplained in more detail elsewhere herein. The UE 120 may determine theCCE-to-REG mapping using the quantity of available RBs or the quantityof available CCEs (rather than the quantity of RBs or CCEs indicated bythe configuration information). For example, the UE 120 may determinethe CCE-to-REG mapping using the quantity of available RBs or thequantity of available CCEs using one or more preconfigured rules (forexample, rules defined, or otherwise fixed, by a wireless communicationstandard, such as the 3GPP). Determining or recalculating the CCE-to-REGmapping using the quantity of available RBs or the quantity of availableCCEs may result in an aggregation level for at least one PDCCH candidateof the CORESET being maintained (for example, as depicted and describedin more detail in connection with FIG. 7B).

In some aspects, the sixth operation 730 may include the UE 120modifying the CCE-to-REG mapping type of the CORESET. For example, theCORESET (as a CORESET 0) may be configured to use interleavingCCE-to-REG mapping. The UE 120 may modify the CCE-to-REG mapping type toa non-interleaving mapping type. The UE 120 may perform the CCE-to-REGmapping for the CORESET using the non-interleaving mapping type. Usingthe non-interleaving mapping type may increase (or maintain) anaggregation level for at least one PDCCH candidate as compared to anaggregation level that would have otherwise been experienced using theinterleaving mapping type (for example, as depicted and described inmore detail in connection with FIG. 7B). In some other aspects, the UE120 may modify the CCE-to-REG mapping type of the CORESET from thenon-interleaving mapping type to the interleaving mapping type. Usingthe interleaving mapping type may increase (or maintain) a quantity ofPDCCH candidates as compared to a quantity of PDCCH candidates thatwould otherwise have been received using the non-interleaving mappingtype. Increasing (or maintaining) the quantity of PDCCH candidates mayincrease (or maintain) a PDCCH capacity associated with the CORESET.

In some aspects, the sixth operation 730 may include the UE 120modifying a frequency range associated with the initial downlinkbandwidth to include the frequency domain resource allocation for theCORESET. The UE 120 may modify the frequency range associated with theinitial downlink bandwidth to include the frequency domain resourceallocation for the CORESET based at least in part on receiving orsuccessfully decoding an SSB. For example, as described elsewhereherein, the CORESET (for example, a CORESET 0) may be multiplexed withan SSB. The base station 110 may transmit, and the UE 120 may receive,the SSB associated with the PDCCH monitoring for initial access (forexample, the SSB associated with, or multiplexed with, the CORESET).After receiving the SSB, the UE 120 may modify the frequency rangeassociated with the initial downlink bandwidth to include the frequencydomain resource allocation for the CORESET. For example, the UE 120 mayshift or hop the range of frequencies associated with the initialdownlink bandwidth to include the frequency domain resource allocationfor the CORESET. In other words, the UE 120 may not increase a size ofthe initial downlink bandwidth, but may modify the range of frequenciesassociated with the initial downlink bandwidth (for example, as depictedand described in more detail in connection with FIG. 7B). Modifying thefrequency range associated with the initial downlink bandwidth mayenable the UE 120 to monitor the full frequency domain resourceallocation for the CORESET and to receive one or more PDCCH messagestransmitted in resource(s) associated with the CORESET.

In some aspects, the UE 120 may identify a precoder granularityassociated with the CORESET. In some aspects, the UE 120 may identifythe precoder granularity associated with the CORESET based at least inpart on one or more action(s) performed by the UE 120 to handle thepartial CORESET. In some aspects, the base station 110 may transmit, andthe UE 120 may receive, an indication of the precoder granularityassociated with the CORESET. In some aspects, the UE 120 may identifythe precoder granularity based at least in part on one or morepreconfigured rules (for example, as defined, or otherwise fixed, by awireless communication standard, such as the 3GPP).

The precoder granularity may indicate a precoding that is to be appliedto REG or RBs associated with the CORESET. For example, the precoderprecoder granularity may indicate that all RBs of an REG (or an REGbundle) use the same precoding. In such examples, each REG or each REGbundle of the CORESET may be associated with a DMRS (which may bereferred to as using local DMRSs). For example, in other contexts, aprecoder granularity that indicates that all RBs of an REG (or an REGbundle) use the same precoding may be indicated via aprecoderGranularityparameter indicating sameAsREG-bundle (for example, as defined, orotherwise fixed, by a wireless communication standard). In some otheraspects, the precoder granularity may indicate that all RBs in theCORESET use the same precoding. In such examples, a single DMRS may beused for all RBs in the CORESET (which may be referred to as using awideband DMRS). For example, in other contexts, a precoder granularitythat indicates that all RBs in the CORESET use the same precoding usethe same precoding may be indicated via a precoderGranularity parameterindicating allContiguousRBs (for example, as defined, or otherwisefixed, by a wireless communication standard).

If the UE 120 identifies (for example, determines or receives anindication that) the precoder granularity associated with the CORESET isall contiguous resource blocks associated with the CORESET (for example,that a wideband DMRS is used), then the UE 120 may receive a DMRS usingavailable resource blocks, or a quantity of available CCEs, in theinitial downlink bandwidth. In other words, if a wideband DMRS is usedfor the CORESET, then the UE 120 may assume that the DMRS is restrictedto the CCEs or RBs that the UE 120 is able to receive (for example, theCCEs or RBs that are within the initial downlink bandwidth).

In a seventh operation 735, the base station 110 may transmit, and theUE 120 may receive, one or more PDCCH messages. The PDCCH messages maybe transmitted using radio resources (time domain resources andfrequency domain resources) associated with the CORESET. The one or morePDCCH messages may include system information, a SIB, an RRC message, ora DCI message, among other examples. For example, in an eighth operation740, the UE 120 may monitor the CORESET and decode the one or more PDCCHmessages. For example, based at least in part on performing one or moreactions described herein, the UE 120 may be enabled to monitor theCORESET (for example, the partial CORESET that was configured at leastpartially outside of the initial downlink bandwidth of the UE 120), orassociated search spaces. The UE 120 may detect a PDCCH message (forexample, in a PDCCH candidate) based at least in part on monitoring theCORESET. The UE 120 may decode and receive the PDCCH message based atleast in part on monitoring the CORESET and detecting the PDCCH message.

The UE 120 may receive the one or more PDCCH messages based at least inpart on performing an action associated with a CORESET that has afrequency domain resource allocation that is at least partially outsideof the initial downlink bandwidth. For example, the UE 120 may receivethe one or more PDCCH messages based at least in part on monitoring theCORESET based at least in part on modifying the resource mapping of theCORESET. In some aspects, the UE 120 may receive the one or more PDCCHmessages based at least in part on monitoring the CORESET based at leastin part on modifying the frequency range associated with the initialdownlink bandwidth.

As shown in FIG. 7B, example actions to be performed by the UE 120 tohandle a partial CORESET are depicted. For example, the CORESET asconfigured in the second operation 710 may be a partial CORESET thatincludes frequency domain resources that are at least partially outsideof the initial downlink bandwidth of the UE 120. For example, as shownin FIG. 7B, the CORESET may include two PDCCH candidates (for example,PDCCH candidate 1 and PDCCH candidate 2). Each PDCCH candidate may havean aggregation level of 4. The CORESET may use an interleavingCCE-to-REG mapping type. As shown in FIG. 7B, the CCE indices of 1, 3,5, and 7 may be outside of the initial downlink bandwidth of the UE 120.

In the sixth operation 730, the UE 120 may perform one or more actions,as described above. For example, the sixth operation 730 may include aninth operation 745. In the ninth operation 745, the UE 120 may modify aresource mapping of the CORESET. For example, the UE 120 may modify theresource mapping by reducing the quantity of RBs or the quantity of CCEsto the quantity of available resources (the available RBs or theavailable CCEs) in the initial downlink bandwidth, as describedelsewhere herein. The UE 120 may perform CCE-to-REG mapping for theCORESET using the reducing quantity of RBs or CCEs. For the exampledepicted in FIG. 7B, this may result in a CCE-to-REG mapping as shown,with CCE indices 0, 1, 2, and 3 being included within the initialdownlink bandwidth. As a result, the aggregation level of the PDCCHcandidate 1 may be maintained at 4 (compared to being reduced to 2 asoriginally configured). In some other aspects, in the ninth operation745 the UE 120 may modify the resource mapping type to thenon-interleaving mapping type. For example, the UE 120 may map CCEs of aPDCCH candidate to consecutive REGs. This may result in a CCE-to-REGmapping as shown, with CCE indices 0, 1, 2, and 3 being included withinthe initial downlink bandwidth. As a result, the aggregation level ofthe PDCCH candidate 1 may be maintained at 4 (compared to being reducedto 2 as originally configured). Therefore, modifying the CCE-to-REGmapping of the CORESET when a portion of the CORESET is outside of theinitial downlink bandwidth may increase an aggregation level of at leastone PDCCH candidate (as compared to the originally configured CORESET).This may improve a communication performance of the UE 120 because theincreased aggregation level is used.

In some aspects, the sixth operation 730 may include a tenth operation750. In the tenth operation 750, the UE 120 may modify a frequency rangeof the initial downlink bandwidth to include the frequency domainresource allocation of the CORESET. For example, after receiving an SSBassociated with the CORESET (for example, a previously transmitted copyof the SSB), the UE 120 may shift the frequency range of the initialdownlink bandwidth to include the frequency domain resource allocationof the CORESET. As shown in FIG. 7B, the UE 120 may not modify a size ofthe initial downlink bandwidth, but may change a range of frequenciesthat are included in the initial downlink bandwidth such that thefrequency domain resource allocation of the CORESET is included withinthe initial downlink bandwidth. As a result, the UE 120 may receive theCORESET with the same quantity of PDCCH candidates as originallyconfigured (for example, thereby maintaining a PDCCH capacity of theCORESET) and may maintain an aggregation level of each PDCCH candidate(for example, thereby improving a performance of the UE 120).

FIG. 8 is a flowchart illustrating an example process 800 performed, forexample, by a UE associated with partial CORESET handling in accordancewith the present disclosure. Example process 800 is an example where theUE (for example, UE 120) performs operations associated with partialCORESET handling.

As shown in FIG. 8 , in some aspects, process 800 may include receivingan indication of an initial downlink bandwidth for the UE (block 810).For example, the UE (such as by using communication manager 140 orreception component 1002, depicted in FIG. 10 ) may receive anindication of an initial downlink bandwidth for the UE, as describedabove.

As further shown in FIG. 8 , in some aspects, process 800 may includereceiving, via an MIB, configuration information for a CORESETassociated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth (block 820). For example, the UE (such as by usingcommunication manager 140 or reception component 1002, depicted in FIG.10 ) may receive, via an MIB, configuration information for a CORESETassociated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth, as described above.

As further shown in FIG. 8 , in some aspects, process 800 may includereceiving one or more PDCCH messages associated with the CORESET basedat least in part on at least one of modifying a resource mapping of theCORESET or modifying the initial downlink bandwidth (block 830). Forexample, the UE (such as by using communication manager 140 or receptioncomponent 1002, depicted in FIG. 10 ) may receive one or more PDCCHmessages associated with the CORESET based at least in part on at leastone of modifying a resource mapping of the CORESET or modifying theinitial downlink bandwidth, as described above.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below or in connection with one ormore other processes described elsewhere herein.

In a first additional aspect, receiving the one or more PDCCH messagesassociated with the CORESET includes modifying the resource mapping ofthe CORESET, and modifying the resource mapping includes performingCCE-to-REG mapping using a quantity of available resource blocks, or aquantity of available CCEs, in the initial downlink bandwidth; andreceiving the one or more PDCCH messages based at least in part onmonitoring the CORESET based at least in part on modifying the resourcemapping.

In a second additional aspect, alone or in combination with the firstaspect, receiving the one or more PDCCH messages associated with theCORESET includes modifying the resource mapping of the CORESET, andmodifying the resource mapping includes modifying a CCE-to-REG mappingtype to a non-interleaving mapping type; and receiving the one or morePDCCH messages based at least in part on monitoring the CORESET based atleast in part on modifying the resource mapping.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, process 800 includes receiving an SSBassociated with the PDCCH monitoring for initial access, and receivingthe one or more PDCCH messages associated with the CORESET includesmodifying a frequency range associated with the initial downlinkbandwidth to include the frequency domain resource allocation for theCORESET based at least in part on receiving the SSB; and receiving theone or more PDCCH messages based at least in part on monitoring theCORESET based at least in part on modifying the frequency rangeassociated with the initial downlink bandwidth.

In a fourth additional aspect, alone or in combination with one or moreof the first through third aspects, receiving the one or more PDCCHmessages associated with the CORESET is based at least in part on one ormore preconfigured rules.

In a fifth additional aspect, alone or in combination with one or moreof the first through fourth aspects, receiving the one or more PDCCHmessages associated with the CORESET includes receiving an indication ofan action to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth, where the action includes at least one of modifyingthe resource mapping of the CORESET or modifying the initial downlinkbandwidth, and receiving the one or more PDCCH messages based at leastin part on performing the action.

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, receiving the indication of theaction includes at least one of receiving the indication of the actionvia a CORESET zero configuration included in a PDCCH configurationindicated by the MIB, receiving the indication of the action via theMIB, receiving the indication of the action via a system informationblock, or receiving the indication of the action via dedicatedsignaling.

In a seventh additional aspect, alone or in combination with one or moreof the first through sixth aspects, process 800 includes receiving anindication of a precoder granularity associated with the CORESET, oridentifying the precoder granularity associated with the CORESET basedat least in part on an action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth.

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the precoder granularityassociated with the CORESET is all contiguous resource blocks associatedwith the CORESET, and receiving the one or more PDCCH messages includesreceiving a DMRS using available resource blocks, or a quantity ofavailable CCEs, in the initial downlink bandwidth.

In a ninth additional aspect, alone or in combination with one or moreof the first through eighth aspects, receiving the one or more PDCCHmessages includes reducing a quantity of resource blocks associated withthe frequency domain resource allocation for the CORESET based at leastin part on a quantity of available resource blocks in the initialdownlink bandwidth, and receiving the one or more PDCCH messages basedat least in part on monitoring the CORESET from a starting resourceblock of the CORESET, where the starting resource block is based atleast in part on reducing the quantity of resource blocks associatedwith the frequency domain resource allocation for the CORESET.

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, receiving the one or more PDCCHmessages includes receiving the one or more PDCCH messages based atleast in part on monitoring the CORESET from a starting resource blockof the CORESET, where the starting resource block is based at least inpart on common resource block index values and a resource block offsetindicated by the configuration information.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, receiving the one or more PDCCHmessages includes receiving the one or more PDCCH messages based atleast in part on monitoring the CORESET from a starting resource blockof the CORESET, where the starting resource block is based at least inpart on virtually extending resource block indices associated with theinitial downlink bandwidth.

In a twelfth additional aspect, alone or in combination with one or moreof the first through eleventh aspects, receiving the one or more PDCCHmessages associated with the CORESET is based at least in part onidentifying a starting resource block of the CORESET, that is outside ofthe initial downlink bandwidth, using one or more preconfigured rules.

In a thirteenth additional aspect, alone or in combination with one ormore of the first through twelfth aspects, process 800 includesreceiving an indication of an action to be performed by the UE toidentify a starting resource block of the CORESET that is outside of theinitial downlink bandwidth.

In a fourteenth additional aspect, alone or in combination with one ormore of the first through thirteenth aspects, receiving the indicationof the action to be performed by the UE to identify the startingresource block of the CORESET includes receiving the indication of theaction via a CORESET zero configuration included in a PDCCHconfiguration indicated by the MIB, receiving the indication of theaction via the MIB, receiving the indication of the action via a systeminformation block, or receiving the indication of the action viadedicated signaling.

In a fifteenth additional aspect, alone or in combination with one ormore of the first through fourteenth aspects, the CORESET is a CORESETzero (CORESET 0).

In a sixteenth additional aspect, alone or in combination with one ormore of the first through fifteenth aspects, the initial downlinkbandwidth is an initial downlink BWP or a maximum downlink bandwidth forthe UE.

In a seventeenth additional aspect, alone or in combination with one ormore of the first through sixteenth aspects, the UE is a reducedcapability UE.

Although FIG. 8 shows example blocks of process 800, in some aspects,process 800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 8 .Additionally or alternatively, two or more of the blocks of process 800may be performed in parallel.

FIG. 9 is a flowchart illustrating an example process 900 performed, forexample, by a base station associated with partial CORESET handling inaccordance with the present disclosure. Example process 900 is anexample where the base station (for example, base station 110) performsoperations associated with partial CORESET handling.

As shown in FIG. 9 , in some aspects, process 900 may includetransmitting, to a UE, an indication of an initial downlink bandwidthfor the UE (block 910). For example, the base station (such as by usingcommunication manager 150 or transmission component 1104, depicted inFIG. 11 ) may transmit, to a UE, an indication of an initial downlinkbandwidth for the UE, as described above.

As further shown in FIG. 9 , in some aspects, process 900 may includetransmitting, to the UE via an MIB, configuration information for aCORESET associated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth (block 920). For example, the base station (such asby using communication manager 150 or transmission component 1104,depicted in FIG. 11 ) may transmit, to the UE via an MIB, configurationinformation for a CORESET associated with PDCCH monitoring for initialaccess, wherein the configuration information indicates a frequencydomain resource allocation for the CORESET, and wherein the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth, as described above.

As further shown in FIG. 9 , in some aspects, process 900 may includetransmitting, to the UE, one or more PDCCH messages associated with theCORESET based at least in part on indicating an action to be performedby the UE when the frequency domain resource allocation for the CORESETis at least partially outside of the initial downlink bandwidth (block930). For example, the base station (such as by using communicationmanager 150 or transmission component 1104, depicted in FIG. 11 ) maytransmit, to the UE, one or more PDCCH messages associated with theCORESET based at least in part on indicating an action to be performedby the UE when the frequency domain resource allocation for the CORESETis at least partially outside of the initial downlink bandwidth, asdescribed above.

Process 900 may include additional aspects, such as any single aspect orany combination of aspects described below or in connection with one ormore other processes described elsewhere herein.

In a first additional aspect, the action to be performed by the UE isbased at least in part on one or more preconfigured rules.

In a second additional aspect, alone or in combination with the firstaspect, transmitting the one or more PDCCH messages associated with theCORESET includes transmitting, to the UE, an indication of the action tobe performed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth, where the action includes at least one of modifying theresource mapping of the CORESET or modifying the initial downlinkbandwidth.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, transmitting the indication of theaction includes at least one of transmitting the indication of theaction via a CORESET zero configuration included in a PDCCHconfiguration indicated by the MIB, transmitting the indication of theaction via the MIB, transmitting the indication of the action via asystem information block, or transmitting the indication of the actionvia dedicated signaling.

In a fourth additional aspect, alone or in combination with one or moreof the first through third aspects, process 900 includes transmitting anindication of a precoder granularity associated with the CORESET.

In a fifth additional aspect, alone or in combination with one or moreof the first through fourth aspects, the action to be performed by theUE is associated with identifying a starting resource block of theCORESET, that is outside of the initial downlink bandwidth, using one ormore preconfigured rules.

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, process 900 includes transmitting anindication of the action to be performed by the UE, where the action isassociated with identifying a starting resource block of the CORESETthat is outside of the initial downlink bandwidth.

In a seventh additional aspect, alone or in combination with one or moreof the first through sixth aspects, transmitting the indication of theaction to be performed by the UE associated with identifying thestarting resource block of the CORESET includes transmitting theindication of the action via a CORESET zero configuration included in aPDCCH configuration indicated by the MIB, transmitting the indication ofthe action via the MIB, transmitting the indication of the action via asystem information block, or transmitting the indication of the actionvia dedicated signaling.

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the action to be performed by theUE associated with identifying the starting resource block of theCORESET includes at least one of reducing a quantity of resource blocksassociated with the frequency domain resource allocation for the CORESETbased at least in part on a quantity of available resource blocks in theinitial downlink bandwidth, identifying the starting resource block ofthe CORESET using common resource block index values and a resourceblock offset indicated by the configuration information, or identifyingthe starting resource block of the CORESET based at least in part onvirtually extending resource block indices associated with the initialdownlink bandwidth.

In a ninth additional aspect, alone or in combination with one or moreof the first through eighth aspects, the CORESET is a CORESET zero(CORESET 0).

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, the initial downlink bandwidth is aninitial downlink bandwidth part (BWP) or a maximum downlink bandwidthfor the UE.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, the UE is a reduced capabilityUE.

Although FIG. 9 shows example blocks of process 900, in some aspects,process 900 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 9 .Additionally or alternatively, two or more of the blocks of process 900may be performed in parallel.

FIG. 10 is a diagram of an example apparatus 1000 for wirelesscommunication in accordance with the present disclosure. The apparatus1000 may be a UE, or a UE may include the apparatus 1000. In someaspects, the apparatus 1000 includes a reception component 1002, atransmission component 1004, and a communication manager 140, which maybe in communication with one another (for example, via one or morebuses). As shown, the apparatus 1000 may communicate with anotherapparatus 1006 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 1002 and thetransmission component 1004.

In some aspects, the apparatus 1000 may be configured to perform one ormore operations described herein in connection with FIGS. 7A and 7B.Additionally or alternatively, the apparatus 1000 may be configured toperform one or more processes described herein, such as process 800 ofFIG. 8 , or a combination thereof. In some aspects, the apparatus 1000may include one or more components of the UE described above inconnection with FIG. 2 .

The reception component 1002 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1006. The reception component1002 may provide received communications to one or more other componentsof the apparatus 1000, such as the communication manager 140. In someaspects, the reception component 1002 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 1002 may include one or more antennas, a modem, a demodulator,a MIMO detector, a receive processor, a controller/processor, a memory,or a combination thereof, of the UE described above in connection withFIG. 2 .

The transmission component 1004 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1006. In some aspects, thecommunication manager 140 may generate communications and may transmitthe generated communications to the transmission component 1004 fortransmission to the apparatus 1006. In some aspects, the transmissioncomponent 1004 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1006. In some aspects, the transmission component 1004may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described above in connection with FIG. 2. In some aspects, the transmission component 1004 may be co-locatedwith the reception component 1002 in a transceiver.

The communication manager 140 may receive or may cause the receptioncomponent 1002 to receive an indication of an initial downlink bandwidthfor the UE. The communication manager 140 may receive or may cause thereception component 1002 to receive, via an MIB, configurationinformation for a CORESET associated with PDCCH monitoring for initialaccess, wherein the configuration information indicates a frequencydomain resource allocation for the CORESET, and wherein the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth. The communication manager 140 mayreceive or may cause the reception component 1002 to receive one or morePDCCH messages associated with the CORESET based at least in part on atleast one of modifying a resource mapping of the CORESET or modifyingthe initial downlink bandwidth. In some aspects, the communicationmanager 140 may perform one or more operations described elsewhereherein as being performed by one or more components of the communicationmanager 140.

The communication manager 140 may include a controller/processor, amemory, or a combination thereof, of the UE described above inconnection with FIG. 2 . In some aspects, the communication manager 140includes a set of components, such as a CORESET handling component 1008,a determination component 1010, or a combination thereof. Alternatively,the set of components may be separate and distinct from thecommunication manager 140. In some aspects, one or more components ofthe set of components may include or may be implemented within acontroller/processor, a memory, or a combination thereof, of the UEdescribed above in connection with FIG. 2 . Additionally oralternatively, one or more components of the set of components may beimplemented at least in part as software stored in a memory. Forexample, a component (or a portion of a component) may be implemented asinstructions or code stored in a non-transitory computer-readable mediumand executable by a controller or a processor to perform the functionsor operations of the component.

The reception component 1002 may receive an indication of an initialdownlink bandwidth for the UE. The reception component 1002 may receive,via an MIB, configuration information for a CORESET associated withPDCCH monitoring for initial access, wherein the configurationinformation indicates a frequency domain resource allocation for theCORESET, and wherein the frequency domain resource allocation for theCORESET is at least partially outside of the initial downlink bandwidth.The reception component 1002 may receive one or more PDCCH messagesassociated with the CORESET based at least in part on at least one ofmodifying a resource mapping of the CORESET or modifying the initialdownlink bandwidth.

The CORESET handling component 1008 may modifying a resource mapping ofthe CORESET. The CORESET handling component 1008 may perform CCE-to-REGmapping using a quantity of available resource blocks, or a quantity ofavailable CCEs, in the initial downlink bandwidth. The CORESET handlingcomponent 1008 may modify a CCE-to-REG mapping type to anon-interleaving mapping type.

The reception component 1002 may receive an SSB associated with thePDCCH monitoring for initial access. The CORESET handling component 1008may modify a frequency range associated with the initial downlinkbandwidth to include the frequency domain resource allocation for theCORESET based at least in part on receiving the SSB.

The reception component 1002 may receive an indication of an action tobe performed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth.

The reception component 1002 may receive an indication of a precodergranularity associated with the CORESET.

The determination component 1010 may identify the precoder granularityassociated with the CORESET based at least in part on an action to beperformed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth.

The reception component 1002 may receive an indication of an action tobe performed by the UE to identify a starting resource block of theCORESET that is outside of the initial downlink bandwidth.

The quantity and arrangement of components shown in FIG. 10 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 10 . Furthermore, two or more components shownin FIG. 10 may be implemented within a single component, or a singlecomponent shown in FIG. 10 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 10 may perform one or more functions describedas being performed by another set of components shown in FIG. 10 .

FIG. 11 is a diagram of an example apparatus 1100 for wirelesscommunication in accordance with the present disclosure. The apparatus1100 may be a base station, or a base station may include the apparatus1100. In some aspects, the apparatus 1100 includes a reception component1102, a transmission component 1104, and a communication manager 150,which may be in communication with one another (for example, via one ormore buses). As shown, the apparatus 1100 may communicate with anotherapparatus 1106 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 1102 and thetransmission component 1104.

In some aspects, the apparatus 1100 may be configured to perform one ormore operations described herein in connection with FIGS. 7A and 7B.Additionally or alternatively, the apparatus 1100 may be configured toperform one or more processes described herein, such as process 900 ofFIG. 9 , or a combination thereof. In some aspects, the apparatus 1100may include one or more components of the base station described abovein connection with FIG. 2 .

The reception component 1102 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1106. The reception component1102 may provide received communications to one or more other componentsof the apparatus 1100, such as the communication manager 150. In someaspects, the reception component 1102 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 1102 may include one or more antennas, a modem, a demodulator,a MIMO detector, a receive processor, a controller/processor, a memory,or a combination thereof, of the base station described above inconnection with FIG. 2 .

The transmission component 1104 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1106. In some aspects, thecommunication manager 150 may generate communications and may transmitthe generated communications to the transmission component 1104 fortransmission to the apparatus 1106. In some aspects, the transmissioncomponent 1104 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1106. In some aspects, the transmission component 1104may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the base station described above in connectionwith FIG. 2 . In some aspects, the transmission component 1104 may beco-located with the reception component 1102 in a transceiver.

The communication manager 150 may transmit or may cause the transmissioncomponent 1104 to transmit, to a UE, an indication of an initialdownlink bandwidth for the UE. The communication manager 150 maytransmit or may cause the transmission component 1104 to transmit, tothe UE via an MIB, configuration information for a CORESET associatedwith PDCCH monitoring for initial access, wherein the configurationinformation indicates a frequency domain resource allocation for theCORESET, and wherein the frequency domain resource allocation for theCORESET is at least partially outside of the initial downlink bandwidth.The communication manager 150 may transmit or may cause the transmissioncomponent 1104 to transmit, to the UE, one or more PDCCH messagesassociated with the CORESET based at least in part on indicating anaction to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth. In some aspects, the communication manager 150 mayperform one or more operations described elsewhere herein as beingperformed by one or more components of the communication manager 150.

The communication manager 150 may include a controller/processor, amemory, a scheduler, a communication unit, or a combination thereof, ofthe base station described above in connection with FIG. 2 . In someaspects, the communication manager 150 includes a set of components,such as a determination component 1108, among other examples.Alternatively, the set of components may be separate and distinct fromthe communication manager 150. In some aspects, one or more componentsof the set of components may include or may be implemented within acontroller/processor, a memory, a scheduler, a communication unit, or acombination thereof, of the base station described above in connectionwith FIG. 2 . Additionally or alternatively, one or more components ofthe set of components may be implemented at least in part as softwarestored in a memory. For example, a component (or a portion of acomponent) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.

The transmission component 1104 may transmit, to a UE, an indication ofan initial downlink bandwidth for the UE. The transmission component1104 may transmit, to the UE via an MIB, configuration information for aCORESET associated with PDCCH monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth. The transmission component 1104 may transmit, to theUE, one or more PDCCH messages associated with the CORESET based atleast in part on indicating an action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth.

The determination component 1108 may determine one or more actions to beperformed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth. The determination component 1108 may determine an action tobe performed by the UE associated with identifying a starting resourceblock of the CORESET that is outside of the initial downlink bandwidth.

The transmission component 1104 may transmit to the UE, an indication ofthe action to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth, wherein the action includes at least one ofmodifying the resource mapping of the CORESET or modifying the initialdownlink bandwidth.

The transmission component 1104 may transmit the indication of theaction via a CORESET zero configuration included in a PDCCHconfiguration indicated by the MIB. The transmission component 1104 maytransmit the indication of the action via the MIB. The transmissioncomponent 1104 may transmit the indication of the action via a systeminformation block. The transmission component 1104 may transmit theindication of the action via dedicated signaling.

The transmission component 1104 may transmit an indication of a precodergranularity associated with the CORESET.

The transmission component 1104 may transmit an indication of the actionto be performed by the UE, where the action is associated withidentifying a starting resource block of the CORESET that is outside ofthe initial downlink bandwidth. The transmission component 1104 maytransmit the indication of the action via a CORESET zero configurationincluded in a PDCCH configuration indicated by the MIB. The transmissioncomponent 1104 may transmit the indication of the action via the MIB.The transmission component 1104 may transmit the indication of theaction via a system information block. The transmission component 1104may transmit the indication of the action via dedicated signaling.

The quantity and arrangement of components shown in FIG. 11 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 11 . Furthermore, two or more components shownin FIG. 11 may be implemented within a single component, or a singlecomponent shown in FIG. 11 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 11 may perform one or more functions describedas being performed by another set of components shown in FIG. 11 .

The following provides an overview of some Aspects of the presentdisclosure:

Aspect 1: A method of wireless communication performed by a userequipment (UE), comprising: receiving an indication of an initialdownlink bandwidth for the UE; receiving, via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and receiving oneor more PDCCH messages associated with the CORESET based at least inpart on at least one of modifying a resource mapping of the CORESET ormodifying the initial downlink bandwidth.

Aspect 2: The method of Aspect 1, wherein receiving the one or morePDCCH messages associated with the CORESET comprises: modifying theresource mapping of the CORESET, wherein modifying the resource mappingincludes performing control channel element (CCE) to resource elementgroup (REG) mapping using a quantity of available resource blocks, or aquantity of available CCEs, in the initial downlink bandwidth; andreceiving the one or more PDCCH messages based at least in part onmonitoring the CORESET based at least in part on modifying the resourcemapping.

Aspect 3: The method of any of Aspects 1-2, wherein receiving the one ormore PDCCH messages associated with the CORESET comprises: modifying theresource mapping of the CORESET, wherein modifying the resource mappingincludes modifying a control channel element (CCE) to resource elementgroup (REG) mapping type to a non-interleaving mapping type; andreceiving the one or more PDCCH messages based at least in part onmonitoring the CORESET based at least in part on modifying the resourcemapping.

Aspect 4: The method of any of Aspects 1-3, further comprising:receiving a synchronization signal block (SSB) associated with the PDCCHmonitoring for initial access; wherein receiving the one or more PDCCHmessages associated with the CORESET comprises: modifying a frequencyrange associated with the initial downlink bandwidth to include thefrequency domain resource allocation for the CORESET based at least inpart on receiving the SSB; and receiving the one or more PDCCH messagesbased at least in part on monitoring the CORESET based at least in parton modifying the frequency range associated with the initial downlinkbandwidth.

Aspect 5: The method of any of Aspects 1-4, wherein receiving the one ormore PDCCH messages associated with the CORESET is based at least inpart on one or more preconfigured rules.

Aspect 6: The method of any of Aspects 1-5, wherein receiving the one ormore PDCCH messages associated with the CORESET comprises: receiving anindication of an action to be performed by the UE when the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth, wherein the action includes at leastone of modifying the resource mapping of the CORESET or modifying theinitial downlink bandwidth; and receiving the one or more PDCCH messagesbased at least in part on performing the action.

Aspect 7: The method of Aspect 6, wherein receiving the indication ofthe action comprises at least one of: receiving the indication of theaction via a CORESET zero configuration included in a PDCCHconfiguration indicated by the MIB; receiving the indication of theaction via the MIB; receiving the indication of the action via a systeminformation block; or receiving the indication of the action viadedicated signaling.

Aspect 8: The method of any of Aspects 1-7, further comprising:receiving an indication of a precoder granularity associated with theCORESET; or identifying the precoder granularity associated with theCORESET based at least in part on an action to be performed by the UEwhen the frequency domain resource allocation for the CORESET is atleast partially outside of the initial downlink bandwidth.

Aspect 9: The method of Aspect 8, wherein the precoder granularityassociated with the CORESET is all contiguous resource blocks associatedwith the CORESET, and wherein receiving the one or more PDCCH messagescomprises: receiving a demodulation reference signal (DMRS) usingavailable resource blocks, or a quantity of available CCEs, in theinitial downlink bandwidth.

Aspect 10: The method of any of Aspects 1-9, wherein receiving the oneor more PDCCH messages comprises: reducing a quantity of resource blocksassociated with the frequency domain resource allocation for the CORESETbased at least in part on a quantity of available resource blocks in theinitial downlink bandwidth; and receiving the one or more PDCCH messagesbased at least in part on monitoring the CORESET from a startingresource block of the CORESET, wherein the starting resource block isbased at least in part on reducing the quantity of resource blocksassociated with the frequency domain resource allocation for theCORESET.

Aspect 11: The method of any of Aspects 1-10, wherein receiving the oneor more PDCCH messages comprises: receiving the one or more PDCCHmessages based at least in part on monitoring the CORESET from astarting resource block of the CORESET, wherein the starting resourceblock is based at least in part on common resource block index valuesand a resource block offset indicated by the configuration information.

Aspect 12: The method of any of Aspects 1-11, wherein receiving the oneor more PDCCH messages comprises: receiving the one or more PDCCHmessages based at least in part on monitoring the CORESET from astarting resource block of the CORESET, wherein the starting resourceblock is based at least in part on virtually extending resource blockindices associated with the initial downlink bandwidth.

Aspect 13: The method of any of Aspects 1-12, wherein receiving the oneor more PDCCH messages associated with the CORESET is based at least inpart on identifying a starting resource block of the CORESET, that isoutside of the initial downlink bandwidth, using one or morepreconfigured rules.

Aspect 14: The method of any of Aspects 1-13, further comprising:receiving an indication of an action to be performed by the UE toidentify a starting resource block of the CORESET that is outside of theinitial downlink bandwidth.

Aspect 15: The method of Aspect 14, wherein receiving the indication ofthe action to be performed by the UE to identify the starting resourceblock of the CORESET comprises: receiving the indication of the actionvia a CORESET zero configuration included in a PDCCH configurationindicated by the MIB; receiving the indication of the action via theMIB; receiving the indication of the action via a system informationblock; or receiving the indication of the action via dedicatedsignaling.

Aspect 16: The method of any of Aspects 1-15, wherein the CORESET is aCORESET zero (CORESET 0).

Aspect 17: The method of any of Aspects 1-16, wherein the initialdownlink bandwidth is an initial downlink bandwidth part (BWP) or amaximum downlink bandwidth for the UE.

Aspect 18: The method of any of Aspects 1-17, wherein the UE is areduced capability UE.

Aspect 19: A method of wireless communication performed by a basestation, comprising: transmitting, to a user equipment (UE), anindication of an initial downlink bandwidth for the UE; transmitting, tothe UE via a master information block (MIB), configuration informationfor a control resource set (CORESET) associated with physical downlinkcontrol channel (PDCCH) monitoring for initial access, wherein theconfiguration information indicates a frequency domain resourceallocation for the CORESET, and wherein the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth; and transmitting, to the UE, one or more PDCCHmessages associated with the CORESET based at least in part onindicating an action to be performed by the UE when the frequency domainresource allocation for the CORESET is at least partially outside of theinitial downlink bandwidth.

Aspect 20: The method of Aspect 19, wherein the action to be performedby the UE is based at least in part on one or more preconfigured rules.

Aspect 21: The method of any of Aspects 19-20, wherein transmitting theone or more PDCCH messages associated with the CORESET comprises:transmitting, to the UE, an indication of the action to be performed bythe UE when the frequency domain resource allocation for the CORESET isat least partially outside of the initial downlink bandwidth, whereinthe action includes at least one of modifying the resource mapping ofthe CORESET or modifying the initial downlink bandwidth.

Aspect 22: The method of Aspect 21, wherein transmitting the indicationof the action comprises at least one of: transmitting the indication ofthe action via a CORESET zero configuration included in a PDCCHconfiguration indicated by the MIB; transmitting the indication of theaction via the MIB; transmitting the indication of the action via asystem information block; or transmitting the indication of the actionvia dedicated signaling.

Aspect 23: The method of any of Aspects 19-22, further comprising:transmitting an indication of a precoder granularity associated with theCORESET.

Aspect 24: The method of any of Aspects 19-23, wherein the action to beperformed by the UE is associated with identifying a starting resourceblock of the CORESET, that is outside of the initial downlink bandwidth,using one or more preconfigured rules.

Aspect 25: The method of any of Aspects 19-24, further comprising:transmitting an indication of the action to be performed by the UE,wherein the action is associated with identifying a starting resourceblock of the CORESET that is outside of the initial downlink bandwidth.

Aspect 26: The method of Aspect 25, wherein transmitting the indicationof the action to be performed by the UE associated with identifying thestarting resource block of the CORESET comprises: transmitting theindication of the action via a CORESET zero configuration included in aPDCCH configuration indicated by the MIB; transmitting the indication ofthe action via the MIB; transmitting the indication of the action via asystem information block; or transmitting the indication of the actionvia dedicated signaling.

Aspect 27: The method of any of Aspects 25-26, wherein the action to beperformed by the UE associated with identifying the starting resourceblock of the CORESET includes at least one of: reducing a quantity ofresource blocks associated with the frequency domain resource allocationfor the CORESET based at least in part on a quantity of availableresource blocks in the initial downlink bandwidth; identifying thestarting resource block of the CORESET using common resource block indexvalues and a resource block offset indicated by the configurationinformation; or identifying the starting resource block of the CORESETbased at least in part on virtually extending resource block indicesassociated with the initial downlink bandwidth.

Aspect 28: The method of any of Aspects 19-27, wherein the CORESET is aCORESET zero (CORESET 0).

Aspect 29: The method of any of Aspects 19-28, wherein the initialdownlink bandwidth is an initial downlink bandwidth part (BWP) or amaximum downlink bandwidth for the UE.

Aspect 30: The method of any of Aspects 19-29, wherein the UE is areduced capability UE.

Aspect 31: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects1-18.

Aspect 32: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 1-18.

Aspect 33: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 1-18.

Aspect 34: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 1-18.

Aspect 35: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 1-18.

Aspect 36: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects19-30.

Aspect 37: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 19-30.

Aspect 38: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 19-30.

Aspect 39: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 19-30.

Aspect 40: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 19-30.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware or a combination of hardware and software. “Software” shallbe construed broadly to mean instructions, instruction sets, code, codesegments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures, orfunctions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardware or acombination of hardware and software. It will be apparent that systemsor methods described herein may be implemented in different forms ofhardware or a combination of hardware and software. The actualspecialized control hardware or software code used to implement thesesystems or methods is not limiting of the aspects. Thus, the operationand behavior of the systems or methods are described herein withoutreference to specific software code, since those skilled in the art willunderstand that software and hardware can be designed to implement thesystems or methods based, at least in part, on the description herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, or not equal to the threshold, amongother examples.

Even though particular combinations of features are recited in theclaims or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsor disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (for example, a+a, a+a+a, a+a+b, a+a+c,a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other orderingof a, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” and similar terms areintended to be open-ended terms that do not limit an element that theymodify (for example, an element “having” A may also have B). Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise. Also, as used herein, the term “or”is intended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (forexample, if used in combination with “either” or “only one of”).

What is claimed is:
 1. A user equipment (UE) for wireless communication,comprising: at least one processor coupled with at least one memory andconfigured to cause the UE to: receive an indication of an initialdownlink bandwidth for the UE; receive, via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and receive one ormore PDCCH messages associated with the CORESET based at least in parton modifying a resource mapping of the CORESET, the modification of theresource mapping of the CORESET including: performing control channelelement (CCE) to resource element group (REG) mapping using a quantityof available resource blocks, or a quantity of available CCEs, in theinitial downlink bandwidth; modifying a control channel element (CCE) toresource element group (REG) mapping type to a non-interleaving mappingtype; or modifying a frequency range associated with the initialdownlink bandwidth to include the frequency domain resource allocationfor the CORESET in accordance with receiving a synchronization signalblock (SSB) associated with the PDCCH monitoring for initial access. 2.A user equipment (UE) for wireless communication, comprising: at leastone processor coupled with at least one memory and configured to causethe UE to: receive an indication of an initial downlink bandwidth forthe UE; receive, via a master information block (MIB), configurationinformation for a control resource set (CORESET) associated withphysical downlink control channel (PDCCH) monitoring for initial access,wherein the configuration information indicates a frequency domainresource allocation for the CORESET, and wherein the frequency domainresource allocation for the CORESET is at least partially outside of theinitial downlink bandwidth; receive an indication of an action to beperformed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth, wherein the action includes at least one of modifying aresource mapping of the CORESET or modifying the initial downlinkbandwidth; and receive one or more PDCCH messages associated with theCORESET based at least in part on performing the action.
 3. The UE ofclaim 2, wherein the at least one memory further storesprocessor-readable code configured to cause the UE to: receive anindication of a precoder granularity associated with the CORESET; oridentify the precoder granularity associated with the CORESET based atleast in part on an action to be performed by the UE when the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth.
 4. A user equipment (UE) for wirelesscommunication, comprising: at least one processor coupled with at leastone memory and configured to cause the UE to: receive an indication ofan initial downlink bandwidth for the UE; receive, via a masterinformation block (MIB), configuration information for a controlresource set (CORESET) associated with physical downlink control channel(PDCCH) monitoring for initial access, wherein the configurationinformation indicates a frequency domain resource allocation for theCORESET, and wherein the frequency domain resource allocation for theCORESET is at least partially outside of the initial downlink bandwidth;reduce a quantity of resource blocks associated with the frequencydomain resource allocation for the CORESET based at least in part on aquantity of available resource blocks in the initial downlink bandwidth;and receive one or more PDCCH messages based at least in part onmonitoring the CORESET from a starting resource block of the CORESET,wherein the starting resource block is based at least in part onreducing the quantity of resource blocks associated with the frequencydomain resource allocation for the CORESET.
 5. A base station forwireless communication, comprising: at least one processor coupled withat least one memory and configured to cause the base station to:transmit, to a user equipment (UE), an indication of an initial downlinkbandwidth for the UE; transmit, to the UE via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; transmit, to theUE, an indication of the action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth, wherein the actionincludes at least one of modifying the resource mapping of the CORESETor modifying the initial downlink bandwidth; and transmit, to the UE,one or more PDCCH messages associated with the CORESET based at least inpart on indicating the action.
 6. A base station for wirelesscommunication, comprising: at least one processor coupled with at leastone memory and configured to cause the base station to: transmit, to auser equipment (UE), an indication of an initial downlink bandwidth forthe UE; transmit, to the UE via a master information block (MIB),configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and transmit anindication of an action to be performed by the UE when the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth, wherein the action is associated withidentifying a starting resource block of the CORESET that is outside ofthe initial downlink bandwidth and wherein the action includes at leastone of: reducing a quantity of resource blocks associated with thefrequency domain resource allocation for the CORESET based at least inpart on a quantity of available resource blocks in the initial downlinkbandwidth; identifying the starting resource block of the CORESET usingcommon resource block index values and a resource block offset indicatedby the configuration information; or identifying the starting resourceblock of the CORESET based at least in part on virtually extendingresource block indices associated with the initial downlink bandwidth.7. A method of wireless communication performed by a user equipment(UE), comprising: receiving an indication of an initial downlinkbandwidth for the UE; receiving, via a master information block (MIB),configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and receiving oneor more PDCCH messages associated with the CORESET based at least inpart on modifying a resource mapping of the CORESET, the modification ofthe resource mapping of the CORESET including: performing controlchannel element (CCE) to resource element group (REG) mapping using aquantity of available resource blocks, or a quantity of available CCEs,in the initial downlink bandwidth; modifying a control channel element(CCE) to resource element group (REG) mapping type to a non-interleavingmapping type; or modifying a frequency range associated with the initialdownlink bandwidth to include the frequency domain resource allocationfor the CORESET in accordance with receiving a synchronization signalblock (SSB) associated with the PDCCH monitoring for initial access. 8.A method of wireless communication performed by a user equipment (UE),comprising: receiving an indication of an initial downlink bandwidth forthe UE; receiving, via a master information block (MIB), configurationinformation for a control resource set (CORESET) associated withphysical downlink control channel (PDCCH) monitoring for initial access,wherein the configuration information indicates a frequency domainresource allocation for the CORESET, and wherein the frequency domainresource allocation for the CORESET is at least partially outside of theinitial downlink bandwidth; receiving an indication of an action to beperformed by the UE when the frequency domain resource allocation forthe CORESET is at least partially outside of the initial downlinkbandwidth, wherein the action includes at least one of modifying aresource mapping of the CORESET or modifying the initial downlinkbandwidth; and receiving one or more PDCCH messages associated with theCORESET based at least in part on performing the action.
 9. The methodof claim 8, further comprising: receiving an indication of a precodergranularity associated with the CORESET; or identifying the precodergranularity associated with the CORESET based at least in part on anaction to be performed by the UE when the frequency domain resourceallocation for the CORESET is at least partially outside of the initialdownlink bandwidth.
 10. A method of wireless communication performed bya user equipment (UE), comprising: receiving an indication of an initialdownlink bandwidth for the UE; receiving, via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; reducing a quantityof resource blocks associated with the frequency domain resourceallocation for the CORESET based at least in part on a quantity ofavailable resource blocks in the initial downlink bandwidth; andreceiving one or more PDCCH messages based at least in part onmonitoring the CORESET from a starting resource block of the CORESET,wherein the starting resource block is based at least in part onreducing the quantity of resource blocks associated with the frequencydomain resource allocation for the CORESET.
 11. A method of wirelesscommunication performed by a base station, comprising: transmitting, toa user equipment (UE), an indication of an initial downlink bandwidthfor the UE; transmitting, to the UE via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; transmitting, tothe UE, an indication of the action to be performed by the UE when thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth, wherein the actionincludes at least one of modifying the resource mapping of the CORESETor modifying the initial downlink bandwidth; and transmitting, to theUE, one or more PDCCH messages associated with the CORESET based atleast in part on indicating the action.
 12. A method of wirelesscommunication performed by a base station, comprising: transmitting, toa user equipment (UE), an indication of an initial downlink bandwidthfor the UE; transmitting, to the UE via a master information block(MIB), configuration information for a control resource set (CORESET)associated with physical downlink control channel (PDCCH) monitoring forinitial access, wherein the configuration information indicates afrequency domain resource allocation for the CORESET, and wherein thefrequency domain resource allocation for the CORESET is at leastpartially outside of the initial downlink bandwidth; and transmitting anindication of an action to be performed by the UE when the frequencydomain resource allocation for the CORESET is at least partially outsideof the initial downlink bandwidth, wherein the action is associated withidentifying a starting resource block of the CORESET that is outside ofthe initial downlink bandwidth and wherein the action includes at leastone of: reducing a quantity of resource blocks associated with thefrequency domain resource allocation for the CORESET based at least inpart on a quantity of available resource blocks in the initial downlinkbandwidth; identifying the starting resource block of the CORESET usingcommon resource block index values and a resource block offset indicatedby the configuration information; or identifying the starting resourceblock of the CORESET based at least in part on virtually extendingresource block indices associated with the initial downlink bandwidth.